drivers/thermal/intel/intel_soc_dts_thermal.c

File Facts

System

Linux kernel

Corpus path

drivers/thermal/intel/intel_soc_dts_thermal.c

Extension

.c

Size

2904 bytes

Lines

110

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/acpi.h
• linux/module.h
• linux/interrupt.h
• asm/cpu_device_id.h
• asm/intel-family.h
• intel_soc_dts_iosf.h

Detected Declarations

• function soc_irq_thread_fn
• function intel_soc_thermal_init
• function intel_soc_thermal_exit
• module init intel_soc_thermal_init

Annotated Snippet

module_init(intel_soc_thermal_init)
module_exit(intel_soc_thermal_exit)

MODULE_DESCRIPTION("Intel SoC DTS Thermal Driver");
MODULE_AUTHOR("Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/module.h`, `linux/interrupt.h`, `asm/cpu_device_id.h`, `asm/intel-family.h`, `intel_soc_dts_iosf.h`.
• Detected declarations: `function soc_irq_thread_fn`, `function intel_soc_thermal_init`, `function intel_soc_thermal_exit`, `module init intel_soc_thermal_init`.
• Atlas domain: Driver Families / drivers/thermal.
• Implementation status: integration implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.