Documentation/devicetree/bindings/net/ieee802154/mcr20a.txt

Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/net/ieee802154/mcr20a.txt

File Facts

System: Linux kernel
Corpus path: Documentation/devicetree/bindings/net/ieee802154/mcr20a.txt
Extension: .txt
Size: 612 bytes
Lines: 24
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 "nxp,mcr20a"
  - spi-max-frequency:	maximal bus speed, should be set to a frequency
			lower than 9000000 depends sync or async operation mode
  - reg:		the chipselect index
  - interrupts:		the interrupt generated by the device. Non high-level
			can occur deadlocks while handling isr.

Optional properties:
  - rst_b-gpio:		GPIO spec for the RST_B pin

Example:

	mcr20a@0 {
		compatible = "nxp,mcr20a";
		spi-max-frequency = <9000000>;
		reg = <0>;
		interrupts = <17 2>;
		interrupt-parent = <&gpio>;
		rst_b-gpio = <&gpio 27 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.