drivers/input/apm-power.c
Source file repositories/reference/linux-study-clean/drivers/input/apm-power.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/input/apm-power.c- Extension
.c- Size
- 2459 bytes
- Lines
- 123
- Domain
- Driver Families
- Bucket
- drivers/input
- 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/module.hlinux/input.hlinux/slab.hlinux/init.hlinux/tty.hlinux/delay.hlinux/pm.hlinux/apm-emulation.h
Detected Declarations
function Copyrightfunction apmpower_eventfunction apmpower_connectfunction apmpower_disconnectfunction apmpower_initfunction apmpower_exitmodule init apmpower_init
Annotated Snippet
module_init(apmpower_init);
module_exit(apmpower_exit);
MODULE_AUTHOR("Richard Purdie <rpurdie@rpsys.net>");
MODULE_DESCRIPTION("Input Power Event -> APM Bridge");
MODULE_LICENSE("GPL");Annotation
- Immediate include surface: `linux/module.h`, `linux/input.h`, `linux/slab.h`, `linux/init.h`, `linux/tty.h`, `linux/delay.h`, `linux/pm.h`, `linux/apm-emulation.h`.
- Detected declarations: `function Copyright`, `function apmpower_event`, `function apmpower_connect`, `function apmpower_disconnect`, `function apmpower_init`, `function apmpower_exit`, `module init apmpower_init`.
- Atlas domain: Driver Families / drivers/input.
- 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.