drivers/clk/qcom/gcc-sc7280.c

Source file repositories/reference/linux-study-clean/drivers/clk/qcom/gcc-sc7280.c

File Facts

System: Linux kernel
Corpus path: drivers/clk/qcom/gcc-sc7280.c
Extension: .c
Size: 92693 bytes
Lines: 3509
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/kernel.h
linux/module.h
linux/of.h
linux/platform_device.h
linux/regmap.h
dt-bindings/clock/qcom,gcc-sc7280.h
clk-alpha-pll.h
clk-branch.h
clk-rcg.h
clk-regmap-divider.h
clk-regmap-mux.h
clk-regmap-phy-mux.h
common.h
gdsc.h
reset.h

Detected Declarations

function gcc_sc7280_probe
function gcc_sc7280_init
function gcc_sc7280_exit
module init gcc_sc7280_init

Annotated Snippet

subsys_initcall(gcc_sc7280_init);

static void __exit gcc_sc7280_exit(void)
{
	platform_driver_unregister(&gcc_sc7280_driver);
}
module_exit(gcc_sc7280_exit);

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

Annotation

Immediate include surface: `linux/clk-provider.h`, `linux/kernel.h`, `linux/module.h`, `linux/of.h`, `linux/platform_device.h`, `linux/regmap.h`, `dt-bindings/clock/qcom,gcc-sc7280.h`, `clk-alpha-pll.h`.
Detected declarations: `function gcc_sc7280_probe`, `function gcc_sc7280_init`, `function gcc_sc7280_exit`, `module init gcc_sc7280_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.