drivers/hwmon/ibmaem.c

File Facts

System

Linux kernel

Corpus path

drivers/hwmon/ibmaem.c

Extension

.c

Size

26845 bytes

Lines

1097

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.
• 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/ipmi.h
• linux/module.h
• linux/hwmon.h
• linux/hwmon-sysfs.h
• linux/jiffies.h
• linux/mutex.h
• linux/kdev_t.h
• linux/spinlock.h
• linux/idr.h
• linux/slab.h
• linux/sched.h
• linux/platform_device.h
• linux/math64.h
• linux/time.h
• linux/err.h

Detected Declarations

• struct aem_ipmi_data
• struct aem_ro_sensor_template
• struct aem_rw_sensor_template
• struct aem_data
• struct aem_iana_id
• struct aem_find_firmware_req
• struct aem_find_firmware_resp
• struct aem_find_instance_req
• struct aem_find_instance_resp
• struct aem_read_sensor_req
• struct aem_read_sensor_resp
• struct aem_driver_data
• function aem_init_ipmi_data
• function aem_send_message
• function aem_msg_handler
• function aem_read_sensor
• function update_aem_energy_one
• function update_aem_energy
• function update_aem1_sensors
• function update_aem2_sensors
• function aem_delete
• function aem_find_aem1_count
• function aem_init_aem1_inst
• function aem_init_aem1
• function aem_find_aem2
• function aem_init_aem2_inst
• function aem_init_aem2
• function aem_register_bmc
• function aem_bmc_gone
• function name_show
• function version_show
• function aem_show_power
• function aem_show_energy
• function aem_show_power_period
• function aem_set_power_period
• function aem_register_sensors
• function aem2_show_temp
• function aem2_show_pcap_value
• function aem_remove_sensors
• function aem1_find_sensors
• function aem2_find_sensors
• function aem_init
• function aem_exit
• module init aem_init

Annotated Snippet

module_init(aem_init);
module_exit(aem_exit);

MODULE_ALIAS("dmi:bvnIBM:*:pnIBMSystemx3350-*");
MODULE_ALIAS("dmi:bvnIBM:*:pnIBMSystemx3550-*");
MODULE_ALIAS("dmi:bvnIBM:*:pnIBMSystemx3650-*");
MODULE_ALIAS("dmi:bvnIBM:*:pnIBMSystemx3655-*");
MODULE_ALIAS("dmi:bvnIBM:*:pnIBMSystemx3755-*");
MODULE_ALIAS("dmi:bvnIBM:*:pnIBM3850M2/x3950M2-*");
MODULE_ALIAS("dmi:bvnIBM:*:pnIBMBladeHC10-*");

Annotation

• Immediate include surface: `linux/ipmi.h`, `linux/module.h`, `linux/hwmon.h`, `linux/hwmon-sysfs.h`, `linux/jiffies.h`, `linux/mutex.h`, `linux/kdev_t.h`, `linux/spinlock.h`.
• Detected declarations: `struct aem_ipmi_data`, `struct aem_ro_sensor_template`, `struct aem_rw_sensor_template`, `struct aem_data`, `struct aem_iana_id`, `struct aem_find_firmware_req`, `struct aem_find_firmware_resp`, `struct aem_find_instance_req`, `struct aem_find_instance_resp`, `struct aem_read_sensor_req`.
• 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.

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.