drivers/char/ipmi/kcs_bmc_serio.c

File Facts

System

Linux kernel

Corpus path

drivers/char/ipmi/kcs_bmc_serio.c

Extension

.c

Size

3801 bytes

Lines

160

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.
• 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/delay.h
• linux/device.h
• linux/errno.h
• linux/list.h
• linux/module.h
• linux/sched/signal.h
• linux/serio.h
• linux/slab.h
• kcs_bmc_client.h

Detected Declarations

• struct kcs_bmc_serio
• function kcs_bmc_serio_event
• function kcs_bmc_serio_open
• function kcs_bmc_serio_close
• function kcs_bmc_serio_add_device
• function kcs_bmc_serio_remove_device
• function kcs_bmc_serio_init
• function kcs_bmc_serio_exit
• module init kcs_bmc_serio_init

Annotated Snippet

module_init(kcs_bmc_serio_init);

static void __exit kcs_bmc_serio_exit(void)
{
	kcs_bmc_unregister_driver(&kcs_bmc_serio_driver);
}
module_exit(kcs_bmc_serio_exit);

MODULE_LICENSE("GPL v2");
MODULE_AUTHOR("Andrew Jeffery <andrew@aj.id.au>");
MODULE_DESCRIPTION("Adapter driver for serio access to BMC KCS devices");

Annotation

• Immediate include surface: `linux/delay.h`, `linux/device.h`, `linux/errno.h`, `linux/list.h`, `linux/module.h`, `linux/sched/signal.h`, `linux/serio.h`, `linux/slab.h`.
• Detected declarations: `struct kcs_bmc_serio`, `function kcs_bmc_serio_event`, `function kcs_bmc_serio_open`, `function kcs_bmc_serio_close`, `function kcs_bmc_serio_add_device`, `function kcs_bmc_serio_remove_device`, `function kcs_bmc_serio_init`, `function kcs_bmc_serio_exit`, `module init kcs_bmc_serio_init`.
• 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.
• 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.