drivers/input/joystick/maplecontrol.c
Source file repositories/reference/linux-study-clean/drivers/input/joystick/maplecontrol.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/input/joystick/maplecontrol.c- Extension
.c- Size
- 4925 bytes
- Lines
- 194
- 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/kernel.hlinux/slab.hlinux/input.hlinux/module.hlinux/init.hlinux/timer.hlinux/maple.h
Detected Declarations
struct dc_padfunction dc_pad_callbackfunction dc_pad_openfunction dc_pad_closefunction probe_maple_controllerfunction remove_maple_controllerfunction dc_pad_initfunction dc_pad_exitmodule init dc_pad_init
Annotated Snippet
module_init(dc_pad_init);
module_exit(dc_pad_exit);Annotation
- Immediate include surface: `linux/kernel.h`, `linux/slab.h`, `linux/input.h`, `linux/module.h`, `linux/init.h`, `linux/timer.h`, `linux/maple.h`.
- Detected declarations: `struct dc_pad`, `function dc_pad_callback`, `function dc_pad_open`, `function dc_pad_close`, `function probe_maple_controller`, `function remove_maple_controller`, `function dc_pad_init`, `function dc_pad_exit`, `module init dc_pad_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.