drivers/input/mouse/rpcmouse.c
Source file repositories/reference/linux-study-clean/drivers/input/mouse/rpcmouse.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/input/mouse/rpcmouse.c- Extension
.c- Size
- 2812 bytes
- Lines
- 114
- 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.
- Touches IRQ or DMA behavior; this matters for the representative real-device path.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/module.hlinux/ptrace.hlinux/interrupt.hlinux/init.hlinux/input.hlinux/io.hmach/hardware.hasm/irq.hasm/hardware/iomd.h
Detected Declarations
function rpcmouse_irqfunction rpcmouse_initfunction rpcmouse_exitmodule init rpcmouse_init
Annotated Snippet
module_init(rpcmouse_init);
module_exit(rpcmouse_exit);Annotation
- Immediate include surface: `linux/module.h`, `linux/ptrace.h`, `linux/interrupt.h`, `linux/init.h`, `linux/input.h`, `linux/io.h`, `mach/hardware.h`, `asm/irq.h`.
- Detected declarations: `function rpcmouse_irq`, `function rpcmouse_init`, `function rpcmouse_exit`, `module init rpcmouse_init`.
- Atlas domain: Driver Families / drivers/input.
- Implementation status: integration implementation candidate.
- IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.
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.