drivers/clk/mxs/clk-imx23.c

File Facts

System

Linux kernel

Corpus path

drivers/clk/mxs/clk-imx23.c

Extension

.c

Size

6421 bytes

Lines

171

Domain

Driver Families

Bucket

drivers/clk

Inferred role

Driver Families: implementation source

Status

source implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/clk/mxs.h
• linux/clk.h
• linux/clk-provider.h
• linux/err.h
• linux/init.h
• linux/io.h
• linux/of.h
• linux/of_address.h
• clk.h

Detected Declarations

• enum imx23_clk
• function clk_misc_init
• function mx23_clocks_init

Annotated Snippet

if (IS_ERR(clks[i])) {
			pr_err("i.MX23 clk %d: register failed with %ld\n",
				i, PTR_ERR(clks[i]));
			return;
		}

	clk_data.clks = clks;
	clk_data.clk_num = ARRAY_SIZE(clks);
	of_clk_add_provider(np, of_clk_src_onecell_get, &clk_data);

	for (i = 0; i < ARRAY_SIZE(clks_init_on); i++)
		clk_prepare_enable(clks[clks_init_on[i]]);

}
CLK_OF_DECLARE(imx23_clkctrl, "fsl,imx23-clkctrl", mx23_clocks_init);

Annotation

• Immediate include surface: `linux/clk/mxs.h`, `linux/clk.h`, `linux/clk-provider.h`, `linux/err.h`, `linux/init.h`, `linux/io.h`, `linux/of.h`, `linux/of_address.h`.
• Detected declarations: `enum imx23_clk`, `function clk_misc_init`, `function mx23_clocks_init`.
• Atlas domain: Driver Families / drivers/clk.
• Implementation status: source implementation candidate.

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.