drivers/macintosh/apm_emu.c
Source file repositories/reference/linux-study-clean/drivers/macintosh/apm_emu.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/macintosh/apm_emu.c- Extension
.c- Size
- 2775 bytes
- Lines
- 109
- Domain
- Driver Families
- Bucket
- drivers/macintosh
- 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.hlinux/module.hlinux/apm-emulation.hlinux/adb.hlinux/pmu.h
Detected Declarations
function Herrenschmidtfunction apm_emu_initfunction apm_emu_exitmodule init apm_emu_init
Annotated Snippet
module_init(apm_emu_init);
module_exit(apm_emu_exit);
MODULE_AUTHOR("Benjamin Herrenschmidt");
MODULE_DESCRIPTION("APM emulation for PowerMac");
MODULE_LICENSE("GPL");
Annotation
- Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/apm-emulation.h`, `linux/adb.h`, `linux/pmu.h`.
- Detected declarations: `function Herrenschmidt`, `function apm_emu_init`, `function apm_emu_exit`, `module init apm_emu_init`.
- Atlas domain: Driver Families / drivers/macintosh.
- 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.