drivers/clk/qcom/gcc-sm6350.c

File Facts

System

Linux kernel

Corpus path

drivers/clk/qcom/gcc-sm6350.c

Extension

.c

Size

66620 bytes

Lines

2599

Domain

Driver Families

Bucket

drivers/clk

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/clk-provider.h
• linux/module.h
• linux/platform_device.h
• linux/regmap.h
• dt-bindings/clock/qcom,gcc-sm6350.h
• clk-alpha-pll.h
• clk-branch.h
• clk-rcg.h
• clk-regmap.h
• clk-regmap-divider.h
• clk-regmap-mux.h
• common.h
• gdsc.h
• reset.h

Detected Declarations

• function gcc_sm6350_probe
• function gcc_sm6350_init
• function gcc_sm6350_exit
• module init gcc_sm6350_init

Annotated Snippet

core_initcall(gcc_sm6350_init);

static void __exit gcc_sm6350_exit(void)
{
	platform_driver_unregister(&gcc_sm6350_driver);
}
module_exit(gcc_sm6350_exit);

MODULE_DESCRIPTION("QTI GCC SM6350 Driver");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/clk-provider.h`, `linux/module.h`, `linux/platform_device.h`, `linux/regmap.h`, `dt-bindings/clock/qcom,gcc-sm6350.h`, `clk-alpha-pll.h`, `clk-branch.h`, `clk-rcg.h`.
• Detected declarations: `function gcc_sm6350_probe`, `function gcc_sm6350_init`, `function gcc_sm6350_exit`, `module init gcc_sm6350_init`.
• Atlas domain: Driver Families / drivers/clk.
• Implementation status: integration 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.