drivers/cpufreq/highbank-cpufreq.c

File Facts

System

Linux kernel

Corpus path

drivers/cpufreq/highbank-cpufreq.c

Extension

.c

Size

2939 bytes

Lines

114

Domain

Driver Families

Bucket

drivers/cpufreq

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/kernel.h
• linux/module.h
• linux/clk.h
• linux/cpu.h
• linux/err.h
• linux/of.h
• linux/pl320-ipc.h
• linux/platform_device.h

Detected Declarations

• function Copyright
• function hb_cpufreq_clk_notify
• function hb_cpufreq_driver_init
• module init hb_cpufreq_driver_init

Annotated Snippet

module_init(hb_cpufreq_driver_init);

static const struct of_device_id __maybe_unused hb_cpufreq_of_match[] = {
	{ .compatible = "calxeda,highbank" },
	{ .compatible = "calxeda,ecx-2000" },
	{ },
};
MODULE_DEVICE_TABLE(of, hb_cpufreq_of_match);

MODULE_AUTHOR("Mark Langsdorf <mark.langsdorf@calxeda.com>");
MODULE_DESCRIPTION("Calxeda Highbank cpufreq driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/clk.h`, `linux/cpu.h`, `linux/err.h`, `linux/of.h`, `linux/pl320-ipc.h`, `linux/platform_device.h`.
• Detected declarations: `function Copyright`, `function hb_cpufreq_clk_notify`, `function hb_cpufreq_driver_init`, `module init hb_cpufreq_driver_init`.
• Atlas domain: Driver Families / drivers/cpufreq.
• 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.