sound/pci/maestro3.c

File Facts

System

Linux kernel

Corpus path

sound/pci/maestro3.c

Extension

.c

Size

81263 bytes

Lines

2713

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/vmalloc.h
• linux/module.h
• linux/firmware.h
• linux/input.h
• sound/core.h
• sound/info.h
• sound/control.h
• sound/pcm.h
• sound/mpu401.h
• sound/ac97_codec.h
• sound/initval.h
• asm/byteorder.h

Detected Declarations

• struct m3_list
• struct m3_dma
• struct assp_instance
• struct snd_m3
• function snd_m3_outw
• function snd_m3_inw
• function snd_m3_outb
• function snd_m3_inb
• function snd_m3_assp_read
• function snd_m3_assp_write
• function snd_m3_assp_halt
• function snd_m3_assp_continue
• function snd_m3_add_list
• function snd_m3_remove_list
• function snd_m3_inc_timer_users
• function snd_m3_dec_timer_users
• function snd_m3_pcm_start
• function snd_m3_pcm_stop
• function snd_m3_pcm_trigger
• function snd_m3_pcm_setup1
• function snd_m3_pcm_setup2
• function snd_m3_playback_setup
• function snd_m3_capture_setup
• function snd_m3_pcm_hw_params
• function snd_m3_pcm_hw_free
• function snd_m3_pcm_prepare
• function snd_m3_get_pointer
• function snd_m3_pcm_pointer
• function snd_m3_update_ptr
• function snd_m3_update_hw_volume
• function snd_m3_interrupt
• function snd_m3_substream_open
• function snd_m3_substream_close
• function snd_m3_playback_open
• function snd_m3_playback_close
• function snd_m3_capture_open
• function snd_m3_capture_close
• function snd_m3_pcm
• function snd_m3_ac97_wait
• function snd_m3_ac97_read
• function snd_m3_ac97_write
• function touched
• function snd_m3_remote_codec_config
• function snd_m3_try_read_vendor
• function snd_m3_ac97_reset
• function snd_m3_mixer
• function snd_m3_assp_init
• function snd_m3_assp_client_init

Annotated Snippet

static struct pci_driver m3_driver = {
	.name = KBUILD_MODNAME,
	.id_table = snd_m3_ids,
	.probe = snd_m3_probe,
	.driver = {
		.pm = &m3_pm,
	},
};
	
module_pci_driver(m3_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/vmalloc.h`.
• Detected declarations: `struct m3_list`, `struct m3_dma`, `struct assp_instance`, `struct snd_m3`, `function snd_m3_outw`, `function snd_m3_inw`, `function snd_m3_outb`, `function snd_m3_inb`, `function snd_m3_assp_read`, `function snd_m3_assp_write`.
• 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.