sound/pci/atiixp_modem.c

File Facts

System

Linux kernel

Corpus path

sound/pci/atiixp_modem.c

Extension

.c

Size

33637 bytes

Lines

1247

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/slab.h
• linux/module.h
• linux/mutex.h
• sound/core.h
• sound/pcm.h
• sound/pcm_params.h
• sound/info.h
• sound/ac97_codec.h
• sound/initval.h

Detected Declarations

• struct atiixp_modem
• struct atiixp_dma_desc
• struct atiixp_dma_ops
• struct atiixp_dma
• struct atiixp_modem
• function snd_atiixp_update_bits
• function atiixp_build_dma_packets
• function atiixp_clear_dma_packets
• function snd_atiixp_acquire_codec
• function snd_atiixp_codec_read
• function snd_atiixp_codec_write
• function snd_atiixp_ac97_read
• function snd_atiixp_ac97_write
• function snd_atiixp_aclink_reset
• function snd_atiixp_aclink_down
• function snd_atiixp_codec_detect
• function snd_atiixp_chip_start
• function snd_atiixp_chip_stop
• function snd_atiixp_pcm_pointer
• function snd_atiixp_xrun_dma
• function snd_atiixp_update_dma
• function snd_atiixp_check_bus_busy
• function snd_atiixp_pcm_trigger
• function atiixp_out_flush_dma
• function atiixp_out_enable_dma
• function atiixp_out_enable_transfer
• function atiixp_in_enable_dma
• function atiixp_in_enable_transfer
• function atiixp_in_flush_dma
• function snd_atiixp_playback_prepare
• function snd_atiixp_capture_prepare
• function snd_atiixp_pcm_hw_params
• function snd_atiixp_pcm_hw_free
• function snd_atiixp_pcm_open
• function snd_atiixp_pcm_close
• function snd_atiixp_playback_open
• function snd_atiixp_playback_close
• function snd_atiixp_capture_open
• function snd_atiixp_capture_close
• function snd_atiixp_pcm_new
• function snd_atiixp_interrupt
• function snd_atiixp_mixer_new
• function snd_atiixp_suspend
• function snd_atiixp_resume
• function snd_atiixp_proc_read
• function snd_atiixp_proc_init
• function snd_atiixp_free
• function snd_atiixp_init

Annotated Snippet

static struct pci_driver atiixp_modem_driver = {
	.name = KBUILD_MODNAME,
	.id_table = snd_atiixp_ids,
	.probe = snd_atiixp_probe,
	.driver = {
		.pm = &snd_atiixp_pm,
	},
};

module_pci_driver(atiixp_modem_driver);

Annotation

• Immediate include surface: `linux/io.h`, `linux/delay.h`, `linux/interrupt.h`, `linux/init.h`, `linux/pci.h`, `linux/slab.h`, `linux/module.h`, `linux/mutex.h`.
• Detected declarations: `struct atiixp_modem`, `struct atiixp_dma_desc`, `struct atiixp_dma_ops`, `struct atiixp_dma`, `struct atiixp_modem`, `function snd_atiixp_update_bits`, `function atiixp_build_dma_packets`, `function atiixp_clear_dma_packets`, `function snd_atiixp_acquire_codec`, `function snd_atiixp_codec_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.