drivers/firmware/efi/efibc.c

File Facts

System

Linux kernel

Corpus path

drivers/firmware/efi/efibc.c

Extension

.c

Size

2204 bytes

Lines

93

Domain

Driver Families

Bucket

drivers/firmware

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/efi.h
• linux/module.h
• linux/reboot.h
• linux/slab.h
• linux/ucs2_string.h

Detected Declarations

• function Copyright
• function efibc_reboot_notifier_call
• function efibc_init
• function efibc_exit
• module init efibc_init

Annotated Snippet

module_init(efibc_init);

static void __exit efibc_exit(void)
{
	unregister_reboot_notifier(&efibc_reboot_notifier);
}
module_exit(efibc_exit);

MODULE_AUTHOR("Jeremy Compostella <jeremy.compostella@intel.com>");
MODULE_AUTHOR("Matt Gumbel <matthew.k.gumbel@intel.com");
MODULE_DESCRIPTION("EFI Bootloader Control");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/efi.h`, `linux/module.h`, `linux/reboot.h`, `linux/slab.h`, `linux/ucs2_string.h`.
• Detected declarations: `function Copyright`, `function efibc_reboot_notifier_call`, `function efibc_init`, `function efibc_exit`, `module init efibc_init`.
• Atlas domain: Driver Families / drivers/firmware.
• 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.