sound/pci/nm256/nm256.c

File Facts

System

Linux kernel

Corpus path

sound/pci/nm256/nm256.c

Extension

.c

Size

42920 bytes

Lines

1654

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.
• 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/info.h
• sound/control.h
• sound/pcm.h
• sound/ac97_codec.h
• sound/initval.h
• nm256_coef.c

Detected Declarations

• struct nm256_stream
• struct nm256
• struct initialValues
• function snd_nm256_readb
• function snd_nm256_readw
• function snd_nm256_readl
• function snd_nm256_writeb
• function snd_nm256_writew
• function snd_nm256_writel
• function snd_nm256_write_buffer
• function snd_nm256_get_start_offset
• function snd_nm256_load_one_coefficient
• function snd_nm256_load_coefficient
• function snd_nm256_fixed_rate
• function snd_nm256_set_format
• function snd_nm256_acquire_irq
• function snd_nm256_release_irq
• function snd_nm256_pcm_mark
• function snd_nm256_playback_start
• function snd_nm256_capture_start
• function snd_nm256_playback_stop
• function snd_nm256_capture_stop
• function snd_nm256_playback_trigger
• function snd_nm256_capture_trigger
• function snd_nm256_pcm_prepare
• function snd_nm256_playback_pointer
• function snd_nm256_capture_pointer
• function snd_nm256_playback_silence
• function snd_nm256_playback_copy
• function snd_nm256_capture_copy
• function snd_nm256_playback_update
• function snd_nm256_capture_update
• function snd_nm256_pcm_hw_params
• function snd_nm256_setup_stream
• function snd_nm256_playback_open
• function snd_nm256_capture_open
• function snd_nm256_playback_close
• function snd_nm256_capture_close
• function snd_nm256_pcm
• function snd_nm256_init_chip
• function snd_nm256_intr_check
• function snd_nm256_interrupt
• function snd_nm256_interrupt_zx
• function snd_nm256_ac97_ready
• function nm256_ac97_idx
• function snd_nm256_ac97_read
• function snd_nm256_ac97_write
• function snd_nm256_ac97_reset

Annotated Snippet

static struct pci_driver nm256_driver = {
	.name = KBUILD_MODNAME,
	.id_table = snd_nm256_ids,
	.probe = snd_nm256_probe,
	.driver = {
		.pm = &nm256_pm,
	},
};

module_pci_driver(nm256_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 nm256_stream`, `struct nm256`, `struct initialValues`, `function snd_nm256_readb`, `function snd_nm256_readw`, `function snd_nm256_readl`, `function snd_nm256_writeb`, `function snd_nm256_writew`, `function snd_nm256_writel`, `function snd_nm256_write_buffer`.
• 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.