sound/pci/es1938.c
Source file repositories/reference/linux-study-clean/sound/pci/es1938.c
File Facts
- System
- Linux kernel
- Corpus path
sound/pci/es1938.c- Extension
.c- Size
- 53270 bytes
- Lines
- 1782
- 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/init.hlinux/interrupt.hlinux/pci.hlinux/slab.hlinux/gameport.hlinux/module.hlinux/delay.hlinux/dma-mapping.hlinux/io.hsound/core.hsound/control.hsound/pcm.hsound/opl3.hsound/mpu401.hsound/initval.hsound/tlv.h
Detected Declarations
struct es1938function snd_es1938_mixer_writefunction snd_es1938_mixer_readfunction registerfunction snd_es1938_write_cmdfunction snd_es1938_get_bytefunction snd_es1938_writefunction snd_es1938_readfunction snd_es1938_bitsfunction snd_es1938_resetfunction snd_es1938_reset_fifofunction snd_es1938_rate_setfunction snd_es1938_playback1_setdmafunction snd_es1938_playback2_setdmafunction snd_es1938_capture_setdmafunction snd_es1938_capture_triggerfunction snd_es1938_playback1_triggerfunction snd_es1938_playback2_triggerfunction snd_es1938_playback_triggerfunction snd_es1938_capture_preparefunction snd_es1938_playback1_preparefunction snd_es1938_playback2_preparefunction snd_es1938_playback_preparefunction snd_es1938_capture_pointerfunction snd_es1938_playback1_pointerfunction snd_es1938_playback2_pointerfunction snd_es1938_playback_pointerfunction snd_es1938_capture_copyfunction snd_es1938_capture_openfunction snd_es1938_playback_openfunction snd_es1938_capture_closefunction snd_es1938_playback_closefunction snd_es1938_new_pcmfunction snd_es1938_info_muxfunction snd_es1938_get_muxfunction snd_es1938_put_muxfunction snd_es1938_get_spatializer_enablefunction snd_es1938_put_spatializer_enablefunction snd_es1938_info_hw_volumefunction snd_es1938_get_hw_volumefunction snd_es1938_get_hw_switchfunction snd_es1938_hwv_freefunction snd_es1938_reg_bitsfunction snd_es1938_reg_readfunction snd_es1938_info_singlefunction snd_es1938_get_singlefunction snd_es1938_put_singlefunction snd_es1938_info_double
Annotated Snippet
static struct pci_driver es1938_driver = {
.name = KBUILD_MODNAME,
.id_table = snd_es1938_ids,
.probe = snd_es1938_probe,
.driver = {
.pm = &es1938_pm,
},
};
module_pci_driver(es1938_driver);
Annotation
- Immediate include surface: `linux/init.h`, `linux/interrupt.h`, `linux/pci.h`, `linux/slab.h`, `linux/gameport.h`, `linux/module.h`, `linux/delay.h`, `linux/dma-mapping.h`.
- Detected declarations: `struct es1938`, `function snd_es1938_mixer_write`, `function snd_es1938_mixer_read`, `function register`, `function snd_es1938_write_cmd`, `function snd_es1938_get_byte`, `function snd_es1938_write`, `function snd_es1938_read`, `function snd_es1938_bits`, `function snd_es1938_reset`.
- 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.