drivers/thermal/thermal_hwmon.h

File Facts

System

Linux kernel

Corpus path

drivers/thermal/thermal_hwmon.h

Extension

.h

Size

1107 bytes

Lines

42

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/thermal.h

Detected Declarations

• function thermal_add_hwmon_sysfs
• function devm_thermal_add_hwmon_sysfs
• function thermal_remove_hwmon_sysfs

Annotated Snippet

#ifndef __THERMAL_HWMON_H__
#define __THERMAL_HWMON_H__

#include <linux/thermal.h>

#ifdef CONFIG_THERMAL_HWMON
int thermal_add_hwmon_sysfs(struct thermal_zone_device *tz);
int devm_thermal_add_hwmon_sysfs(struct device *dev, struct thermal_zone_device *tz);
void thermal_remove_hwmon_sysfs(struct thermal_zone_device *tz);
#else
static inline int
thermal_add_hwmon_sysfs(struct thermal_zone_device *tz)
{
	return 0;
}

static inline int
devm_thermal_add_hwmon_sysfs(struct device *dev, struct thermal_zone_device *tz)
{
	return 0;
}

static inline void
thermal_remove_hwmon_sysfs(struct thermal_zone_device *tz)
{
}
#endif

#endif /* __THERMAL_HWMON_H__ */

Annotation

• Immediate include surface: `linux/thermal.h`.
• Detected declarations: `function thermal_add_hwmon_sysfs`, `function devm_thermal_add_hwmon_sysfs`, `function thermal_remove_hwmon_sysfs`.
• Atlas domain: Driver Families / drivers/thermal.
• 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.