sound/pci/fm801.c

File Facts

System

Linux kernel

Corpus path

sound/pci/fm801.c

Extension

.c

Size

40716 bytes

Lines

1406

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/delay.h
• linux/init.h
• linux/interrupt.h
• linux/io.h
• linux/pci.h
• linux/slab.h
• linux/module.h
• sound/core.h
• sound/pcm.h
• sound/tlv.h
• sound/ac97_codec.h
• sound/mpu401.h
• sound/opl3.h
• sound/initval.h
• media/drv-intf/tea575x.h

Detected Declarations

• struct fm801
• struct snd_fm801_tea575x_gpio
• function fm801_iowrite16
• function fm801_ioread16
• function fm801_ac97_is_ready
• function fm801_ac97_is_valid
• function snd_fm801_update_bits
• function snd_fm801_codec_write
• function snd_fm801_codec_read
• function snd_fm801_rate_bits
• function snd_fm801_playback_trigger
• function snd_fm801_capture_trigger
• function snd_fm801_playback_prepare
• function snd_fm801_capture_prepare
• function snd_fm801_playback_pointer
• function snd_fm801_capture_pointer
• function snd_fm801_interrupt
• function scoped_guard
• function scoped_guard
• function snd_fm801_playback_open
• function snd_fm801_capture_open
• function snd_fm801_playback_close
• function snd_fm801_capture_close
• function snd_fm801_pcm
• function snd_fm801_tea575x_set_pins
• function snd_fm801_tea575x_get_pins
• function snd_fm801_tea575x_set_direction
• function snd_fm801_info_single
• function snd_fm801_get_single
• function snd_fm801_put_single
• function snd_fm801_info_double
• function snd_fm801_get_double
• function snd_fm801_put_double
• function snd_fm801_info_mux
• function snd_fm801_get_mux
• function snd_fm801_put_mux
• function snd_fm801_mixer
• function wait_for_codec
• function reset_codec
• function snd_fm801_chip_multichannel_init
• function snd_fm801_chip_init
• function snd_fm801_free
• function snd_fm801_create
• function __snd_card_fm801_probe
• function snd_card_fm801_probe
• function snd_fm801_suspend
• function snd_fm801_resume

Annotated Snippet

static struct pci_driver fm801_driver = {
	.name = KBUILD_MODNAME,
	.id_table = snd_fm801_ids,
	.probe = snd_card_fm801_probe,
	.driver = {
		.pm = &snd_fm801_pm,
	},
};

module_pci_driver(fm801_driver);

Annotation

• Immediate include surface: `linux/delay.h`, `linux/init.h`, `linux/interrupt.h`, `linux/io.h`, `linux/pci.h`, `linux/slab.h`, `linux/module.h`, `sound/core.h`.
• Detected declarations: `struct fm801`, `struct snd_fm801_tea575x_gpio`, `function fm801_iowrite16`, `function fm801_ioread16`, `function fm801_ac97_is_ready`, `function fm801_ac97_is_valid`, `function snd_fm801_update_bits`, `function snd_fm801_codec_write`, `function snd_fm801_codec_read`, `function snd_fm801_rate_bits`.
• 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.