drivers/thermal/intel/intel_soc_dts_iosf.h

File Facts

System

Linux kernel

Corpus path

drivers/thermal/intel/intel_soc_dts_iosf.h

Extension

.h

Size

1232 bytes

Lines

51

Domain

Driver Families

Bucket

drivers/thermal

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.
• 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/thermal.h

Detected Declarations

• struct intel_soc_dts_sensors
• struct intel_soc_dts_sensor_entry
• struct intel_soc_dts_sensors
• enum intel_soc_dts_interrupt_type

Annotated Snippet

struct intel_soc_dts_sensor_entry {
	int id;
	u32 store_status;
	struct thermal_zone_device *tzone;
	struct intel_soc_dts_sensors *sensors;
};

struct intel_soc_dts_sensors {
	u32 tj_max;
	spinlock_t intr_notify_lock;
	struct mutex dts_update_lock;
	enum intel_soc_dts_interrupt_type intr_type;
	struct intel_soc_dts_sensor_entry soc_dts[SOC_MAX_DTS_SENSORS];
};


struct intel_soc_dts_sensors *
intel_soc_dts_iosf_init(enum intel_soc_dts_interrupt_type intr_type,
			bool critical_trip, int crit_offset);
void intel_soc_dts_iosf_exit(struct intel_soc_dts_sensors *sensors);
void intel_soc_dts_iosf_interrupt_handler(
				struct intel_soc_dts_sensors *sensors);
#endif

Annotation

• Immediate include surface: `linux/thermal.h`.
• Detected declarations: `struct intel_soc_dts_sensors`, `struct intel_soc_dts_sensor_entry`, `struct intel_soc_dts_sensors`, `enum intel_soc_dts_interrupt_type`.
• Atlas domain: Driver Families / drivers/thermal.
• Implementation status: source 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.