Documentation/devicetree/bindings/clock/st/st,clkgen-mux.txt

File Facts

System

Linux kernel

Corpus path

Documentation/devicetree/bindings/clock/st/st,clkgen-mux.txt

Extension

.txt

Size

778 bytes

Lines

33

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

Binding for a ST multiplexed clock driver.

This binding supports only simple indexed multiplexers, it does not
support table based parent index to hardware value translations.

This binding uses the common clock binding[1].

[1] Documentation/devicetree/bindings/clock/clock-bindings.txt

Required properties:

- compatible : shall be:
	"st,stih407-clkgen-a9-mux"

- #clock-cells : from common clock binding; shall be set to 0.

- reg : A Base address and length of the register set.

- clocks : from common clock binding

Example:

	clk_m_a9: clk-m-a9@92b0000 {
		#clock-cells = <0>;
		compatible = "st,stih407-clkgen-a9-mux";
		reg = <0x92b0000 0x10000>;

		clocks = <&clockgen_a9_pll 0>,
			 <&clockgen_a9_pll 0>,
			 <&clk_s_c0_flexgen 13>,
			 <&clk_m_a9_ext2f_div2>;
	};

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.