drivers/char/ipmi/ipmi_ssif.c
Source file repositories/reference/linux-study-clean/drivers/char/ipmi/ipmi_ssif.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/char/ipmi/ipmi_ssif.c- Extension
.c- Size
- 57390 bytes
- Lines
- 2208
- 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.
- 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/modversions.hlinux/module.hlinux/moduleparam.hlinux/sched.hlinux/seq_file.hlinux/timer.hlinux/delay.hlinux/errno.hlinux/spinlock.hlinux/slab.hlinux/list.hlinux/i2c.hlinux/ipmi_smi.hlinux/init.hlinux/dmi.hlinux/kthread.hlinux/acpi.hlinux/ctype.hlinux/time64.hipmi_dmi.h
Detected Declarations
struct ssif_addr_infostruct ssif_infostruct ssif_infoenum ssif_intf_stateenum ssif_stat_indexesfunction ipmi_ssif_unlock_condfunction deliver_recv_msgfunction return_hosed_msgfunction start_clear_flagsfunction start_flag_fetchfunction check_start_sendfunction start_event_fetchfunction start_recv_msg_fetchfunction handle_flagsfunction ipmi_ssif_threadfunction ssif_i2c_sendfunction start_getfunction retry_timeoutfunction watch_timeoutfunction ssif_alertfunction msg_done_handlerfunction msg_written_handlerfunction start_resendfunction start_sendfunction start_next_msgfunction senderfunction get_smi_infofunction request_eventsfunction ssif_set_need_watchfunction ssif_start_processingfunction DEVICE_ATTRfunction shutdown_ssiffunction ssif_removefunction list_for_each_entryfunction read_responsefunction do_cmdfunction ssif_detectfunction strcmp_nospacefunction check_acpifunction find_slave_addressfunction start_multipart_testfunction test_multipart_messagesfunction ssif_remove_dupfunction ssif_add_infosfunction ssif_check_and_removefunction list_for_each_entryfunction ssif_probefunction ipmi_register_smi
Annotated Snippet
module_init(init_ipmi_ssif);
static void __exit cleanup_ipmi_ssif(void)
{
if (!initialized)
return;
initialized = false;
i2c_del_driver(&ssif_i2c_driver);
kfree(ssif_i2c_driver.address_list);
if (ssif_trydmi && platform_registered)
platform_driver_unregister(&ipmi_driver);
free_ssif_clients();
}
module_exit(cleanup_ipmi_ssif);
MODULE_ALIAS("platform:dmi-ipmi-ssif");
MODULE_AUTHOR("Todd C Davis <todd.c.davis@intel.com>, Corey Minyard <minyard@acm.org>");
MODULE_DESCRIPTION("IPMI driver for management controllers on a SMBus");
MODULE_LICENSE("GPL");
Annotation
- Immediate include surface: `linux/modversions.h`, `linux/module.h`, `linux/moduleparam.h`, `linux/sched.h`, `linux/seq_file.h`, `linux/timer.h`, `linux/delay.h`, `linux/errno.h`.
- Detected declarations: `struct ssif_addr_info`, `struct ssif_info`, `struct ssif_info`, `enum ssif_intf_state`, `enum ssif_stat_indexes`, `function ipmi_ssif_unlock_cond`, `function deliver_recv_msg`, `function return_hosed_msg`, `function start_clear_flags`, `function start_flag_fetch`.
- Atlas domain: Driver Families / drivers/char.
- 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.