Documentation/devicetree/bindings/mmc/moxa,moxart-mmc.txt

File Facts

System

Linux kernel

Corpus path

Documentation/devicetree/bindings/mmc/moxa,moxart-mmc.txt

Extension

.txt

Size

740 bytes

Lines

31

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

MOXA ART MMC Host Controller Interface

  Inherits from mmc binding[1].

  [1] Documentation/devicetree/bindings/mmc/mmc.txt

Required properties:

- compatible :	Must be "moxa,moxart-mmc" or "faraday,ftsdc010"
- reg :		Should contain registers location and length
- interrupts :	Should contain the interrupt number
- clocks :	Should contain phandle for the clock feeding the MMC controller

Optional properties:

- dmas :	Should contain two DMA channels, line request number must be 5 for
		both channels
- dma-names :	Must be "tx", "rx"

Example:

	mmc: mmc@98e00000 {
		compatible = "moxa,moxart-mmc";
		reg = <0x98e00000 0x5C>;
		interrupts = <5 0>;
		clocks = <&clk_apb>;
		dmas =  <&dma 5>,
			<&dma 5>;
		dma-names = "tx", "rx";
	};

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.