drivers/input/gameport/lightning.c
Source file repositories/reference/linux-study-clean/drivers/input/gameport/lightning.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/input/gameport/lightning.c- Extension
.c- Size
- 6168 bytes
- Lines
- 323
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
asm/io.hlinux/delay.hlinux/errno.hlinux/ioport.hlinux/kernel.hlinux/module.hlinux/init.hlinux/gameport.h
Detected Declarations
struct l4function l4_wait_readyfunction l4_cooked_readfunction l4_openfunction l4_getcalfunction l4_setcalfunction l4_calibratefunction l4_create_portsfunction l4_add_cardfunction l4_initfunction l4_exitmodule init l4_init
Annotated Snippet
module_init(l4_init);
module_exit(l4_exit);Annotation
- Immediate include surface: `asm/io.h`, `linux/delay.h`, `linux/errno.h`, `linux/ioport.h`, `linux/kernel.h`, `linux/module.h`, `linux/init.h`, `linux/gameport.h`.
- Detected declarations: `struct l4`, `function l4_wait_ready`, `function l4_cooked_read`, `function l4_open`, `function l4_getcal`, `function l4_setcal`, `function l4_calibrate`, `function l4_create_ports`, `function l4_add_card`, `function l4_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.