Documentation/devicetree/bindings/sound/soc-ac97link.txt

File Facts

System

Linux kernel

Corpus path

Documentation/devicetree/bindings/sound/soc-ac97link.txt

Extension

.txt

Size

725 bytes

Lines

29

Domain

Support Tooling And Documentation

Bucket

Documentation

Inferred role

Support Tooling And Documentation: documentation

Status

atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

AC97 link bindings

These bindings can be included within any other device node.

Required properties:
 - pinctrl-names: Has to contain following states to setup the correct
   pinmuxing for the used gpios:
	"ac97-running": AC97-link is active
	"ac97-reset": AC97-link reset state
	"ac97-warm-reset": AC97-link warm reset state
 - ac97-gpios: List of gpio phandles with args in the order ac97-sync,
   ac97-sdata, ac97-reset


Example:

ssi {
	...

	pinctrl-names = "default", "ac97-running", "ac97-reset", "ac97-warm-reset";
	pinctrl-0 = <&ac97link_running>;
	pinctrl-1 = <&ac97link_running>;
	pinctrl-2 = <&ac97link_reset>;
	pinctrl-3 = <&ac97link_warm_reset>;
	ac97-gpios = <&gpio3 20 0 &gpio3 22 0 &gpio3 28 0>;

	...
};

Annotation

• Atlas domain: Support Tooling And Documentation / Documentation.
• Implementation status: atlas-only.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.