sound/pci/au88x0/au88x0_game.c

File Facts

System

Linux kernel

Corpus path

sound/pci/au88x0/au88x0_game.c

Extension

.c

Size

2955 bytes

Lines

122

Domain

Driver Families

Bucket

sound/pci

Inferred role

Driver Families: implementation source

Status

source 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 or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/time.h
• linux/delay.h
• linux/init.h
• sound/core.h
• au88x0.h
• linux/gameport.h
• linux/export.h

Detected Declarations

• function vortex_game_read
• function vortex_game_trigger
• function vortex_game_cooked_read
• function vortex_game_open
• function vortex_gameport_register
• function vortex_gameport_unregister
• function vortex_gameport_register
• function vortex_gameport_unregister

Annotated Snippet

static inline int vortex_gameport_register(vortex_t * vortex) { return -ENOSYS; }
static inline void vortex_gameport_unregister(vortex_t * vortex) { }
#endif

Annotation

• Immediate include surface: `linux/time.h`, `linux/delay.h`, `linux/init.h`, `sound/core.h`, `au88x0.h`, `linux/gameport.h`, `linux/export.h`.
• Detected declarations: `function vortex_game_read`, `function vortex_game_trigger`, `function vortex_game_cooked_read`, `function vortex_game_open`, `function vortex_gameport_register`, `function vortex_gameport_unregister`, `function vortex_gameport_register`, `function vortex_gameport_unregister`.
• Atlas domain: Driver Families / sound/pci.
• Implementation status: source 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.