drivers/cpufreq/cpufreq-dt.h

File Facts

System

Linux kernel

Corpus path

drivers/cpufreq/cpufreq-dt.h

Extension

.h

Size

679 bytes

Lines

28

Domain

Driver Families

Bucket

drivers/cpufreq

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/types.h

Detected Declarations

• struct cpufreq_policy
• struct cpufreq_dt_platform_data

Annotated Snippet

struct cpufreq_dt_platform_data {
	bool have_governor_per_policy;

	unsigned int	(*get_intermediate)(struct cpufreq_policy *policy,
					    unsigned int index);
	int		(*target_intermediate)(struct cpufreq_policy *policy,
					       unsigned int index);
	int (*suspend)(struct cpufreq_policy *policy);
	int (*resume)(struct cpufreq_policy *policy);
};

struct platform_device *cpufreq_dt_pdev_register(struct device *dev);

#endif /* __CPUFREQ_DT_H__ */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct cpufreq_policy`, `struct cpufreq_dt_platform_data`.
• Atlas domain: Driver Families / drivers/cpufreq.
• 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.