drivers/input/gameport/emu10k1-gp.c

File Facts

System

Linux kernel

Corpus path

drivers/input/gameport/emu10k1-gp.c

Extension

.c

Size

2375 bytes

Lines

109

Domain

Driver Families

Bucket

drivers/input

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• 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.h
• linux/module.h
• linux/ioport.h
• linux/gameport.h
• linux/slab.h
• linux/pci.h

Detected Declarations

• struct emu
• function emu_probe
• function emu_remove

Annotated Snippet

static struct pci_driver emu_driver = {
        .name =         "Emu10k1_gameport",
        .id_table =     emu_tbl,
        .probe =        emu_probe,
	.remove =	emu_remove,
};

module_pci_driver(emu_driver);

Annotation

• Immediate include surface: `asm/io.h`, `linux/module.h`, `linux/ioport.h`, `linux/gameport.h`, `linux/slab.h`, `linux/pci.h`.
• Detected declarations: `struct emu`, `function emu_probe`, `function emu_remove`.
• Atlas domain: Driver Families / drivers/input.
• Implementation status: pattern 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.