drivers/char/ipmi/ipmi_si_pci.c

File Facts

System

Linux kernel

Corpus path

drivers/char/ipmi/ipmi_si_pci.c

Extension

.c

Size

3699 bytes

Lines

166

Domain

Driver Families

Bucket

drivers/char

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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 an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• linux/pci.h
• ipmi_si.h

Detected Declarations

• function ipmi_pci_probe_regspacing
• function ipmi_pci_probe
• function ipmi_pci_remove
• function ipmi_si_pci_init
• function ipmi_si_pci_shutdown

Annotated Snippet

static struct pci_driver ipmi_pci_driver = {
	.name =         SI_DEVICE_NAME,
	.id_table =     ipmi_pci_devices,
	.probe =        ipmi_pci_probe,
	.remove =       ipmi_pci_remove,
};

void ipmi_si_pci_init(void)
{
	if (si_trypci) {
		int rv = pci_register_driver(&ipmi_pci_driver);
		if (rv)
			pr_err("Unable to register PCI driver: %d\n", rv);
		else
			pci_registered = true;
	}
}

void ipmi_si_pci_shutdown(void)
{
	if (pci_registered)
		pci_unregister_driver(&ipmi_pci_driver);
}

Annotation

• Immediate include surface: `linux/module.h`, `linux/pci.h`, `ipmi_si.h`.
• Detected declarations: `function ipmi_pci_probe_regspacing`, `function ipmi_pci_probe`, `function ipmi_pci_remove`, `function ipmi_si_pci_init`, `function ipmi_si_pci_shutdown`.
• Atlas domain: Driver Families / drivers/char.
• Implementation status: pattern 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.