drivers/char/ipmi/kcs_bmc.h
Source file repositories/reference/linux-study-clean/drivers/char/ipmi/kcs_bmc.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/char/ipmi/kcs_bmc.h- Extension
.h- Size
- 809 bytes
- Lines
- 47
- Domain
- Driver Families
- Bucket
- drivers/char
- Inferred role
- Driver Families: implementation source
- Status
- source 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/list.h
Detected Declarations
struct kcs_ioregstruct kcs_bmc_device_opsstruct kcs_bmc_clientstruct kcs_bmc_device
Annotated Snippet
struct kcs_ioreg {
u32 idr;
u32 odr;
u32 str;
};
struct kcs_bmc_device_ops;
struct kcs_bmc_client;
struct kcs_bmc_device {
struct list_head entry;
struct device *dev;
u32 channel;
struct kcs_ioreg ioreg;
const struct kcs_bmc_device_ops *ops;
spinlock_t lock;
struct kcs_bmc_client *client;
};
#endif /* __KCS_BMC_H__ */
Annotation
- Immediate include surface: `linux/list.h`.
- Detected declarations: `struct kcs_ioreg`, `struct kcs_bmc_device_ops`, `struct kcs_bmc_client`, `struct kcs_bmc_device`.
- Atlas domain: Driver Families / drivers/char.
- Implementation status: source 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.