sound/pci/sonicvibes.c

File Facts

System

Linux kernel

Corpus path

sound/pci/sonicvibes.c

Extension

.c

Size

49040 bytes

Lines

1450

Domain

Driver Families

Bucket

sound/pci

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• 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/delay.h
• linux/init.h
• linux/interrupt.h
• linux/pci.h
• linux/slab.h
• linux/gameport.h
• linux/module.h
• linux/dma-mapping.h
• linux/io.h
• sound/core.h
• sound/pcm.h
• sound/info.h
• sound/control.h
• sound/mpu401.h
• sound/opl3.h
• sound/initval.h

Detected Declarations

• struct sonicvibes
• function snd_sonicvibes_setdmaa
• function snd_sonicvibes_setdmac
• function snd_sonicvibes_getdmaa
• function snd_sonicvibes_getdmac
• function snd_sonicvibes_out1
• function snd_sonicvibes_out
• function snd_sonicvibes_in1
• function snd_sonicvibes_in
• function snd_sonicvibes_debug
• function snd_sonicvibes_setfmt
• function snd_sonicvibes_pll
• function snd_sonicvibes_setpll
• function snd_sonicvibes_set_adc_rate
• function snd_sonicvibes_hw_constraint_dac_rate
• function snd_sonicvibes_set_dac_rate
• function snd_sonicvibes_trigger
• function snd_sonicvibes_interrupt
• function scoped_guard
• function snd_sonicvibes_playback_trigger
• function snd_sonicvibes_capture_trigger
• function snd_sonicvibes_playback_prepare
• function snd_sonicvibes_capture_prepare
• function snd_sonicvibes_playback_pointer
• function snd_sonicvibes_capture_pointer
• function snd_sonicvibes_playback_open
• function snd_sonicvibes_capture_open
• function snd_sonicvibes_playback_close
• function snd_sonicvibes_capture_close
• function snd_sonicvibes_pcm
• function snd_sonicvibes_info_mux
• function snd_sonicvibes_get_mux
• function snd_sonicvibes_put_mux
• function snd_sonicvibes_info_single
• function snd_sonicvibes_get_single
• function snd_sonicvibes_put_single
• function snd_sonicvibes_info_double
• function snd_sonicvibes_get_double
• function snd_sonicvibes_put_double
• function snd_sonicvibes_master_free
• function snd_sonicvibes_mixer
• function snd_sonicvibes_proc_read
• function snd_sonicvibes_proc_init
• function snd_sonicvibes_create_gameport
• function snd_sonicvibes_free_gameport
• function snd_sonicvibes_create_gameport
• function snd_sonicvibes_free_gameport
• function snd_sonicvibes_create

Annotated Snippet

static struct pci_driver sonicvibes_driver = {
	.name = KBUILD_MODNAME,
	.id_table = snd_sonic_ids,
	.probe = snd_sonic_probe,
};

module_pci_driver(sonicvibes_driver);

Annotation

• Immediate include surface: `linux/delay.h`, `linux/init.h`, `linux/interrupt.h`, `linux/pci.h`, `linux/slab.h`, `linux/gameport.h`, `linux/module.h`, `linux/dma-mapping.h`.
• Detected declarations: `struct sonicvibes`, `function snd_sonicvibes_setdmaa`, `function snd_sonicvibes_setdmac`, `function snd_sonicvibes_getdmaa`, `function snd_sonicvibes_getdmac`, `function snd_sonicvibes_out1`, `function snd_sonicvibes_out`, `function snd_sonicvibes_in1`, `function snd_sonicvibes_in`, `function snd_sonicvibes_debug`.
• Atlas domain: Driver Families / sound/pci.
• Implementation status: pattern implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• 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.