Documentation/devicetree/bindings/dma/milbeaut-m10v-xdmac.txt

File Facts

System

Linux kernel

Corpus path

Documentation/devicetree/bindings/dma/milbeaut-m10v-xdmac.txt

Extension

.txt

Size

727 bytes

Lines

25

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

Milbeaut AXI DMA controller has only memory to memory transfer capability.

* DMA controller

Required property:
- compatible: 	Should be  "socionext,milbeaut-m10v-xdmac"
- reg:		Should contain DMA registers location and length.
- interrupts: 	Should contain all of the per-channel DMA interrupts.
                Number of channels is configurable - 2, 4 or 8, so
                the number of interrupts specified should be {2,4,8}.
- #dma-cells: 	Should be 1.

Example:
	xdmac0: dma-controller@1c250000 {
		compatible = "socionext,milbeaut-m10v-xdmac";
		reg = <0x1c250000 0x1000>;
		interrupts = <0 17 0x4>,
			     <0 18 0x4>,
			     <0 19 0x4>,
			     <0 20 0x4>;
		#dma-cells = <1>;
	};

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.