include/sound/emu10k1_synth.h
Source file repositories/reference/linux-study-clean/include/sound/emu10k1_synth.h
File Facts
- System
- Linux kernel
- Corpus path
include/sound/emu10k1_synth.h- Extension
.h- Size
- 693 bytes
- Lines
- 27
- Domain
- Driver Families
- Bucket
- include/sound
- 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.
- 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
sound/emu10k1.hsound/emux_synth.h
Detected Declarations
struct snd_emu10k1_synth_arg
Annotated Snippet
struct snd_emu10k1_synth_arg {
struct snd_emu10k1 *hwptr; /* chip */
int index; /* sequencer client index */
int seq_ports; /* number of sequencer ports to be created */
int max_voices; /* maximum number of voices for wavetable */
};
#define EMU10K1_MAX_MEMSIZE (32 * 1024 * 1024) /* 32MB */
#endif
Annotation
- Immediate include surface: `sound/emu10k1.h`, `sound/emux_synth.h`.
- Detected declarations: `struct snd_emu10k1_synth_arg`.
- Atlas domain: Driver Families / include/sound.
- Implementation status: source 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.