sound/pci/mixart/mixart.c

File Facts

System

Linux kernel

Corpus path

sound/pci/mixart/mixart.c

Extension

.c

Size

38269 bytes

Lines

1391

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.
• Touches user memory; correctness depends on fault-safe copying and privilege boundary handling.
• 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/init.h
• linux/interrupt.h
• linux/pci.h
• linux/dma-mapping.h
• linux/module.h
• linux/mutex.h
• linux/slab.h
• sound/core.h
• sound/initval.h
• sound/info.h
• sound/control.h
• sound/pcm.h
• sound/pcm_params.h
• mixart.h
• mixart_hwdep.h
• mixart_core.h
• mixart_mixer.h

Detected Declarations

• function mixart_set_pipe_state
• function mixart_set_clock
• function IOs
• function snd_mixart_kill_ref_pipe
• function mixart_set_stream_state
• function snd_mixart_trigger
• function mixart_sync_nonblock_events
• function snd_mixart_prepare
• function mixart_set_format
• function snd_mixart_hw_params
• function snd_mixart_hw_free
• function snd_mixart_playback_open
• function snd_mixart_capture_open
• function snd_mixart_close
• function snd_mixart_stream_pointer
• function preallocate_buffers
• function snd_mixart_pcm_analog
• function snd_mixart_pcm_digital
• function snd_mixart_chip_free
• function snd_mixart_chip_dev_free
• function snd_mixart_create
• function snd_mixart_create_pcm
• function snd_mixart_free
• function snd_mixart_BA0_read
• function snd_mixart_BA1_read
• function snd_mixart_proc_read
• function snd_mixart_proc_init
• function snd_mixart_probe
• function snd_mixart_remove

Annotated Snippet

static struct pci_driver mixart_driver = {
	.name = KBUILD_MODNAME,
	.id_table = snd_mixart_ids,
	.probe = snd_mixart_probe,
	.remove = snd_mixart_remove,
};

module_pci_driver(mixart_driver);

Annotation

• Immediate include surface: `linux/init.h`, `linux/interrupt.h`, `linux/pci.h`, `linux/dma-mapping.h`, `linux/module.h`, `linux/mutex.h`, `linux/slab.h`, `sound/core.h`.
• Detected declarations: `function mixart_set_pipe_state`, `function mixart_set_clock`, `function IOs`, `function snd_mixart_kill_ref_pipe`, `function mixart_set_stream_state`, `function snd_mixart_trigger`, `function mixart_sync_nonblock_events`, `function snd_mixart_prepare`, `function mixart_set_format`, `function snd_mixart_hw_params`.
• Atlas domain: Driver Families / sound/pci.
• Implementation status: pattern implementation candidate.
• This snippet crosses the user/kernel memory boundary; validate fault handling and access checks before translating the pattern.
• 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.