drivers/hwmon/hwmon.c

File Facts

System

Linux kernel

Corpus path

drivers/hwmon/hwmon.c

Extension

.c

Size

35766 bytes

Lines

1347

Domain

Driver Families

Bucket

drivers/hwmon

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/bitops.h
• linux/device.h
• linux/err.h
• linux/gfp.h
• linux/hwmon.h
• linux/i2c.h
• linux/idr.h
• linux/kstrtox.h
• linux/list.h
• linux/module.h
• linux/mutex.h
• linux/pci.h
• linux/property.h
• linux/slab.h
• linux/string.h
• linux/thermal.h
• trace/events/hwmon.h

Detected Declarations

• struct hwmon_device
• struct hwmon_device_attribute
• struct hwmon_thermal_data
• function name_show
• function label_show
• function hwmon_dev_attr_is_visible
• function hwmon_free_attrs
• function hwmon_dev_release
• function hwmon_is_visible
• function hwmon_thermal_get_temp
• function hwmon_thermal_set_trips
• function hwmon_thermal_remove_sensor
• function hwmon_thermal_add_sensor
• function hwmon_thermal_register_sensors
• function hwmon_thermal_notify
• function list_for_each_entry
• function hwmon_attr_base
• function hwmon_match_device
• function pec_show
• function pec_store
• function hwmon_remove_pec
• function hwmon_pec_register
• function hwmon_pec_register
• function hwmon_attr_show
• function hwmon_attr_show_string
• function hwmon_attr_store
• function is_string_attr
• function hwmon_notify_event
• function hwmon_lock
• function hwmon_unlock
• function hwmon_num_channel_attrs
• function hwmon_genattrs
• function __hwmon_create_attrs
• function __hwmon_device_register
• function hwmon_device_unregister
• function hwmon_device_unregister
• function hwmon_device_unregister
• function hwmon_device_unregister
• function hwmon_device_unregister
• function devm_hwmon_release
• function devm_hwmon_device_register_with_groups
• function devm_hwmon_device_register_with_info
• function hwmon_pci_quirks
• function hwmon_init
• function hwmon_exit
• module init hwmon_init
• export hwmon_notify_event
• export hwmon_lock

Annotated Snippet

subsys_initcall(hwmon_init);
module_exit(hwmon_exit);

MODULE_AUTHOR("Mark M. Hoffman <mhoffman@lightlink.com>");
MODULE_DESCRIPTION("hardware monitoring sysfs/class support");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/bitops.h`, `linux/device.h`, `linux/err.h`, `linux/gfp.h`, `linux/hwmon.h`, `linux/i2c.h`, `linux/idr.h`, `linux/kstrtox.h`.
• Detected declarations: `struct hwmon_device`, `struct hwmon_device_attribute`, `struct hwmon_thermal_data`, `function name_show`, `function label_show`, `function hwmon_dev_attr_is_visible`, `function hwmon_free_attrs`, `function hwmon_dev_release`, `function hwmon_is_visible`, `function hwmon_thermal_get_temp`.
• Atlas domain: Driver Families / drivers/hwmon.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• 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.