sound/pci/intel8x0.c

File Facts

System

Linux kernel

Corpus path

sound/pci/intel8x0.c

Extension

.c

Size

89842 bytes

Lines

3266

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

Detected Declarations

• struct ichdev
• struct intel8x0
• struct ich_pcm_table
• struct ich_reg_info
• function igetbyte
• function igetword
• function igetdword
• function iputbyte
• function iputword
• function iputdword
• function iagetword
• function iaputword
• function snd_intel8x0_codec_semaphore
• function snd_intel8x0_codec_write
• function snd_intel8x0_codec_read
• function snd_intel8x0_codec_read_test
• function snd_intel8x0_ali_codec_ready
• function snd_intel8x0_ali_codec_semaphore
• function snd_intel8x0_ali_codec_read
• function snd_intel8x0_ali_codec_write
• function snd_intel8x0_setup_periods
• function snd_intel8x0_update
• function scoped_guard
• function snd_intel8x0_interrupt
• function snd_intel8x0_pcm_trigger
• function snd_intel8x0_ali_trigger
• function snd_intel8x0_hw_params
• function snd_intel8x0_hw_free
• function snd_intel8x0_setup_pcm_out
• function snd_intel8x0_pcm_prepare
• function snd_intel8x0_pcm_pointer
• function snd_intel8x0_pcm_open
• function snd_intel8x0_playback_open
• function snd_intel8x0_playback_close
• function snd_intel8x0_capture_open
• function snd_intel8x0_capture_close
• function snd_intel8x0_mic_open
• function snd_intel8x0_mic_close
• function snd_intel8x0_mic2_open
• function snd_intel8x0_mic2_close
• function snd_intel8x0_capture2_open
• function snd_intel8x0_capture2_close
• function snd_intel8x0_spdif_open
• function snd_intel8x0_spdif_close
• function snd_intel8x0_ali_ac97spdifout_open
• function scoped_guard
• function snd_intel8x0_ali_ac97spdifout_close
• function snd_intel8x0_ali_spdifin_open

Annotated Snippet

static struct pci_driver intel8x0_driver = {
	.name = KBUILD_MODNAME,
	.id_table = snd_intel8x0_ids,
	.probe = snd_intel8x0_probe,
	.driver = {
		.pm = &intel8x0_pm,
	},
};

module_pci_driver(intel8x0_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`, `sound/core.h`.
• Detected declarations: `struct ichdev`, `struct intel8x0`, `struct ich_pcm_table`, `struct ich_reg_info`, `function igetbyte`, `function igetword`, `function igetdword`, `function iputbyte`, `function iputword`, `function iputdword`.
• 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.