drivers/acpi/bgrt.c

File Facts

System

Linux kernel

Corpus path

drivers/acpi/bgrt.c

Extension

.c

Size

2123 bytes

Lines

95

Domain

Driver Families

Bucket

drivers/acpi

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kernel.h
• linux/init.h
• linux/device.h
• linux/sysfs.h
• linux/efi-bgrt.h

Detected Declarations

• function acpi_parse_bgrt
• function bgrt_init
• module init bgrt_init

Annotated Snippet

device_initcall(bgrt_init);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/init.h`, `linux/device.h`, `linux/sysfs.h`, `linux/efi-bgrt.h`.
• Detected declarations: `function acpi_parse_bgrt`, `function bgrt_init`, `module init bgrt_init`.
• Atlas domain: Driver Families / drivers/acpi.
• 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.