Documentation/devicetree/bindings/xillybus/xillybus.txt
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/xillybus/xillybus.txt
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/xillybus/xillybus.txt- Extension
.txt- Size
- 508 bytes
- Lines
- 19
- 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
Required properties:
- compatible: Should be "xillybus,xillybus-1.00.a"
- reg: Address and length of the register set for the device
- interrupts: Contains one interrupt node, typically consisting of three cells.
Optional properties:
- dma-coherent: Present if DMA operations are coherent
Example:
xillybus@ff200400 {
compatible = "xillybus,xillybus-1.00.a";
reg = < 0xff200400 0x00000080 >;
interrupts = < 0 40 1 >;
interrupt-parent = <&intc>;
} ;
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.