Documentation/devicetree/bindings/sound/marvell,pxa2xx-ac97.txt
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/sound/marvell,pxa2xx-ac97.txt
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/sound/marvell,pxa2xx-ac97.txt- Extension
.txt- Size
- 826 bytes
- Lines
- 28
- 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
Marvell PXA2xx audio complex
This descriptions matches the AC97 controller found in pxa2xx and pxa3xx series.
Required properties:
- compatible: should be one of the following:
"marvell,pxa250-ac97"
"marvell,pxa270-ac97"
"marvell,pxa300-ac97"
- reg: device MMIO address space
- interrupts: single interrupt generated by AC97 IP
- clocks: input clock of the AC97 IP, refer to clock-bindings.txt
Optional properties:
- pinctrl-names, pinctrl-0: refer to pinctrl-bindings.txt
- reset-gpios: gpio used for AC97 reset, refer to gpio.txt
Example:
ac97: sound@40500000 {
compatible = "marvell,pxa250-ac97";
reg = < 0x40500000 0x1000 >;
interrupts = <14>;
reset-gpios = <&gpio 113 GPIO_ACTIVE_HIGH>;
#sound-dai-cells = <1>;
pinctrl-names = "default";
pinctrl-0 = < &pmux_ac97_default >;
};
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.