sound/pci/echoaudio/echoaudio.c

File Facts

System

Linux kernel

Corpus path

sound/pci/echoaudio/echoaudio.c

Extension

.c

Size

58999 bytes

Lines

2213

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/module.h
• linux/string.h

Detected Declarations

• function get_firmware
• function free_firmware
• function free_firmware_cache
• function audiopipe_free
• function hw_rule_capture_format_by_channels
• function hw_rule_capture_channels_by_format
• function hw_rule_playback_format_by_channels
• function hw_rule_playback_channels_by_format
• function hw_rule_sample_rate
• function pcm_open
• function pcm_analog_in_open
• function pcm_analog_out_open
• function pcm_digital_in_open
• function pcm_digital_out_open
• function pcm_close
• function init_engine
• function pcm_analog_in_hw_params
• function pcm_analog_out_hw_params
• function pcm_digital_in_hw_params
• function pcm_digital_out_hw_params
• function pcm_hw_free
• function pcm_prepare
• function pcm_trigger
• function snd_pcm_group_for_each_entry
• function pcm_pointer
• function snd_echo_preallocate_pages
• function snd_echo_new_pcm
• function snd_echo_output_gain_info
• function snd_echo_output_gain_get
• function snd_echo_output_gain_put
• function snd_echo_input_gain_info
• function snd_echo_input_gain_get
• function snd_echo_input_gain_put
• function snd_echo_output_nominal_info
• function snd_echo_output_nominal_get
• function snd_echo_output_nominal_put
• function snd_echo_input_nominal_info
• function snd_echo_input_nominal_get
• function snd_echo_input_nominal_put
• function snd_echo_mixer_info
• function snd_echo_mixer_get
• function snd_echo_mixer_put
• function snd_echo_vmixer_info
• function snd_echo_vmixer_get
• function snd_echo_vmixer_put
• function snd_echo_digital_mode_info
• function snd_echo_digital_mode_get
• function snd_echo_digital_mode_put

Annotated Snippet

static struct pci_driver echo_driver = {
	.name = KBUILD_MODNAME,
	.id_table = snd_echo_ids,
	.probe = snd_echo_probe,
	.driver = {
		.pm = &snd_echo_pm,
	},
};

module_pci_driver(echo_driver);

Annotation

• Immediate include surface: `linux/module.h`, `linux/string.h`.
• Detected declarations: `function get_firmware`, `function free_firmware`, `function free_firmware_cache`, `function audiopipe_free`, `function hw_rule_capture_format_by_channels`, `function hw_rule_capture_channels_by_format`, `function hw_rule_playback_format_by_channels`, `function hw_rule_playback_channels_by_format`, `function hw_rule_sample_rate`, `function pcm_open`.
• 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.