drivers/input/gameport/ns558.c
Source file repositories/reference/linux-study-clean/drivers/input/gameport/ns558.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/input/gameport/ns558.c- Extension
.c- Size
- 6374 bytes
- Lines
- 268
- 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
asm/io.hlinux/module.hlinux/ioport.hlinux/init.hlinux/delay.hlinux/gameport.hlinux/slab.hlinux/pnp.h
Detected Declarations
struct ns558function ns558_isa_probefunction ns558_pnp_probefunction ns558_initfunction ns558_exitfunction list_for_each_entry_safemodule init ns558_init
Annotated Snippet
module_init(ns558_init);
module_exit(ns558_exit);Annotation
- Immediate include surface: `asm/io.h`, `linux/module.h`, `linux/ioport.h`, `linux/init.h`, `linux/delay.h`, `linux/gameport.h`, `linux/slab.h`, `linux/pnp.h`.
- Detected declarations: `struct ns558`, `function ns558_isa_probe`, `function ns558_pnp_probe`, `function ns558_init`, `function ns558_exit`, `function list_for_each_entry_safe`, `module init ns558_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.