drivers/devfreq/governor_simpleondemand.c

File Facts

System

Linux kernel

Corpus path

drivers/devfreq/governor_simpleondemand.c

Extension

.c

Size

3442 bytes

Lines

145

Domain

Driver Families

Bucket

drivers/devfreq

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/errno.h
• linux/module.h
• linux/devfreq.h
• linux/devfreq-governor.h
• linux/math64.h

Detected Declarations

• function Copyright
• function devfreq_simple_ondemand_handler
• function devfreq_simple_ondemand_init
• function devfreq_simple_ondemand_exit
• module init devfreq_simple_ondemand_init

Annotated Snippet

subsys_initcall(devfreq_simple_ondemand_init);

static void __exit devfreq_simple_ondemand_exit(void)
{
	int ret;

	ret = devfreq_remove_governor(&devfreq_simple_ondemand);
	if (ret)
		pr_err("%s: failed remove governor %d\n", __func__, ret);

	return;
}
module_exit(devfreq_simple_ondemand_exit);
MODULE_DESCRIPTION("DEVFREQ Simple On-demand governor");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/errno.h`, `linux/module.h`, `linux/devfreq.h`, `linux/devfreq-governor.h`, `linux/math64.h`.
• Detected declarations: `function Copyright`, `function devfreq_simple_ondemand_handler`, `function devfreq_simple_ondemand_init`, `function devfreq_simple_ondemand_exit`, `module init devfreq_simple_ondemand_init`.
• Atlas domain: Driver Families / drivers/devfreq.
• 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.