drivers/thermal/intel/intel_tcc_cooling.c

File Facts

System

Linux kernel

Corpus path

drivers/thermal/intel/intel_tcc_cooling.c

Extension

.c

Size

3151 bytes

Lines

130

Domain

Driver Families

Bucket

drivers/thermal

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/device.h
• linux/intel_tcc.h
• linux/module.h
• linux/thermal.h
• asm/cpu_device_id.h
• asm/msr.h

Detected Declarations

• function tcc_get_max_state
• function tcc_get_cur_state
• function tcc_set_cur_state
• function tcc_cooling_init
• function tcc_cooling_exit
• module init tcc_cooling_init

Annotated Snippet

module_init(tcc_cooling_init)

static void __exit tcc_cooling_exit(void)
{
	thermal_cooling_device_unregister(tcc_cdev);
}

module_exit(tcc_cooling_exit)

MODULE_IMPORT_NS("INTEL_TCC");
MODULE_DESCRIPTION("TCC offset cooling device Driver");
MODULE_AUTHOR("Zhang Rui <rui.zhang@intel.com>");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/device.h`, `linux/intel_tcc.h`, `linux/module.h`, `linux/thermal.h`, `asm/cpu_device_id.h`, `asm/msr.h`.
• Detected declarations: `function tcc_get_max_state`, `function tcc_get_cur_state`, `function tcc_set_cur_state`, `function tcc_cooling_init`, `function tcc_cooling_exit`, `module init tcc_cooling_init`.
• Atlas domain: Driver Families / drivers/thermal.
• 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.