drivers/acpi/fan.h
Source file repositories/reference/linux-study-clean/drivers/acpi/fan.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/acpi/fan.h- Extension
.h- Size
- 3250 bytes
- Lines
- 115
- Domain
- Driver Families
- Bucket
- drivers/acpi
- 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/kconfig.hlinux/limits.h
Detected Declarations
struct acpi_fan_fpsstruct acpi_fan_fifstruct acpi_fan_fststruct acpi_fanfunction acpi_fan_speed_validfunction acpi_fan_speed_validfunction devm_acpi_fan_create_hwmonfunction acpi_fan_notify_hwmon
Annotated Snippet
struct acpi_fan_fps {
u64 control;
u64 trip_point;
u64 speed;
u64 noise_level;
u64 power;
char name[ACPI_FPS_NAME_LEN];
struct device_attribute dev_attr;
};
struct acpi_fan_fif {
u8 revision;
u8 fine_grain_ctrl;
u8 step_size;
u8 low_speed_notification;
};
struct acpi_fan_fst {
u64 revision;
u64 control;
u64 speed;
};
struct acpi_fan {
acpi_handle handle;
bool acpi4;
bool has_fst;
struct acpi_fan_fif fif;
struct acpi_fan_fps *fps;
int fps_count;
/* A value of 0 means that trippoint-related functions are not supported */
u32 fan_trip_granularity;
#if IS_REACHABLE(CONFIG_HWMON)
struct device *hdev;
#endif
struct thermal_cooling_device *cdev;
struct device_attribute fst_speed;
struct device_attribute fine_grain_control;
};
/**
* acpi_fan_speed_valid - Check if fan speed value is valid
* @speeed: Speed value returned by the ACPI firmware
*
* Check if the fan speed value returned by the ACPI firmware is valid. This function is
* necessary as ACPI firmware implementations can return 0xFFFFFFFF to signal that the
* ACPI fan does not support speed reporting. Additionally, some buggy ACPI firmware
* implementations return a value larger than the 32-bit integer value defined by
* the ACPI specification when using placeholder values. Such invalid values are also
* detected by this function.
*
* Returns: True if the fan speed value is valid, false otherwise.
*/
static inline bool acpi_fan_speed_valid(u64 speed)
{
return speed < U32_MAX;
}
/**
* acpi_fan_power_valid - Check if fan power value is valid
* @power: Power value returned by the ACPI firmware
*
* Check if the fan power value returned by the ACPI firmware is valid.
* See acpi_fan_speed_valid() for details.
*
* Returns: True if the fan power value is valid, false otherwise.
*/
static inline bool acpi_fan_power_valid(u64 power)
{
return power < U32_MAX;
}
int acpi_fan_get_fst(acpi_handle handle, struct acpi_fan_fst *fst);
int acpi_fan_create_attributes(struct acpi_device *device);
void acpi_fan_delete_attributes(struct acpi_device *device);
#if IS_REACHABLE(CONFIG_HWMON)
int devm_acpi_fan_create_hwmon(struct device *dev);
void acpi_fan_notify_hwmon(struct device *dev);
#else
static inline int devm_acpi_fan_create_hwmon(struct device *dev) { return 0; };
static inline void acpi_fan_notify_hwmon(struct device *dev) { };
#endif
#endif
Annotation
- Immediate include surface: `linux/kconfig.h`, `linux/limits.h`.
- Detected declarations: `struct acpi_fan_fps`, `struct acpi_fan_fif`, `struct acpi_fan_fst`, `struct acpi_fan`, `function acpi_fan_speed_valid`, `function acpi_fan_speed_valid`, `function devm_acpi_fan_create_hwmon`, `function acpi_fan_notify_hwmon`.
- Atlas domain: Driver Families / drivers/acpi.
- 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.