sound/pci/es1968.c

File Facts

System

Linux kernel

Corpus path

sound/pci/es1968.c

Extension

.c

Size

76846 bytes

Lines

2818

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.
• 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

• linux/io.h
• linux/delay.h
• linux/interrupt.h
• linux/init.h
• linux/pci.h
• linux/dma-mapping.h
• linux/slab.h
• linux/gameport.h
• linux/module.h
• linux/mutex.h
• linux/input.h
• sound/core.h
• sound/pcm.h
• sound/mpu401.h
• sound/ac97_codec.h
• sound/initval.h
• media/drv-intf/tea575x.h

Detected Declarations

• struct esm_memory
• struct esschan
• struct es1968
• struct snd_es1968_tea575x_gpio
• struct ess_device_list
• enum snd_enum_apu_type
• function __maestro_write
• function maestro_write
• function __maestro_read
• function maestro_read
• function snd_es1968_ac97_wait
• function snd_es1968_ac97_wait_poll
• function snd_es1968_ac97_write
• function snd_es1968_ac97_read
• function apu_index_set
• function apu_data_set
• function __apu_set_register
• function apu_set_register
• function __apu_get_register
• function apu_get_register
• function assp_set_register
• function assp_get_register
• function wave_set_register
• function wave_get_register
• function snd_es1968_bob_stop
• function snd_es1968_bob_start
• function snd_es1968_bob_inc
• function snd_es1968_bob_dec
• function list_for_each_entry
• function snd_es1968_calc_bob_rate
• function snd_es1968_compute_rate
• function snd_es1968_get_dma_ptr
• function snd_es1968_apu_set_freq
• function snd_es1968_trigger_apu
• function snd_es1968_pcm_start
• function snd_es1968_pcm_stop
• function snd_es1968_program_wavecache
• function snd_es1968_playback_setup
• function scoped_guard
• function init_capture_apu
• function snd_es1968_capture_setup
• function snd_es1968_pcm_prepare
• function snd_es1968_pcm_trigger
• function snd_es1968_pcm_pointer
• function calc_available_memory_size
• function snd_es1968_free_memory
• function snd_es1968_free_dmabuf
• function snd_es1968_init_dmabuf

Annotated Snippet

static struct pci_driver es1968_driver = {
	.name = KBUILD_MODNAME,
	.id_table = snd_es1968_ids,
	.probe = snd_es1968_probe,
	.driver = {
		.pm = &es1968_pm,
	},
};

module_pci_driver(es1968_driver);

Annotation

• Immediate include surface: `linux/io.h`, `linux/delay.h`, `linux/interrupt.h`, `linux/init.h`, `linux/pci.h`, `linux/dma-mapping.h`, `linux/slab.h`, `linux/gameport.h`.
• Detected declarations: `struct esm_memory`, `struct esschan`, `struct es1968`, `struct snd_es1968_tea575x_gpio`, `struct ess_device_list`, `enum snd_enum_apu_type`, `function __maestro_write`, `function maestro_write`, `function __maestro_read`, `function maestro_read`.
• 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.