drivers/char/ipmi/ipmi_dmi.c

File Facts

System

Linux kernel

Corpus path

drivers/char/ipmi/ipmi_dmi.c

Extension

.c

Size

5269 bytes

Lines

224

Domain

Driver Families

Bucket

drivers/char

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.
• 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/init.h
• linux/dmi.h
• linux/platform_device.h
• linux/property.h
• ipmi_dmi.h
• ipmi_plat_data.h

Detected Declarations

• struct ipmi_dmi_info
• function dmi_add_platform_ipmi
• function ipmi_dmi_get_slave_addr
• function dmi_decode_ipmi
• function scan_for_dmi_ipmi
• module init scan_for_dmi_ipmi
• export ipmi_dmi_get_slave_addr

Annotated Snippet

subsys_initcall(scan_for_dmi_ipmi);

Annotation

• Immediate include surface: `linux/ipmi.h`, `linux/init.h`, `linux/dmi.h`, `linux/platform_device.h`, `linux/property.h`, `ipmi_dmi.h`, `ipmi_plat_data.h`.
• Detected declarations: `struct ipmi_dmi_info`, `function dmi_add_platform_ipmi`, `function ipmi_dmi_get_slave_addr`, `function dmi_decode_ipmi`, `function scan_for_dmi_ipmi`, `module init scan_for_dmi_ipmi`, `export ipmi_dmi_get_slave_addr`.
• Atlas domain: Driver Families / drivers/char.
• Implementation status: integration 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.