sound/pci/ymfpci/ymfpci.c

File Facts

System

Linux kernel

Corpus path

sound/pci/ymfpci/ymfpci.c

Extension

.c

Size

10243 bytes

Lines

367

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/init.h
• linux/pci.h
• linux/time.h
• linux/module.h
• sound/core.h
• ymfpci.h
• sound/mpu401.h
• sound/opl3.h
• sound/initval.h

Detected Declarations

• function snd_ymfpci_create_gameport
• function snd_ymfpci_free_gameport
• function snd_ymfpci_create_gameport
• function snd_ymfpci_free_gameport
• function snd_card_ymfpci_probe

Annotated Snippet

static struct pci_driver ymfpci_driver = {
	.name = KBUILD_MODNAME,
	.id_table = snd_ymfpci_ids,
	.probe = snd_card_ymfpci_probe,
	.driver = {
		.pm = pm_sleep_ptr(&snd_ymfpci_pm),
	},
};

module_pci_driver(ymfpci_driver);

Annotation

• Immediate include surface: `linux/init.h`, `linux/pci.h`, `linux/time.h`, `linux/module.h`, `sound/core.h`, `ymfpci.h`, `sound/mpu401.h`, `sound/opl3.h`.
• Detected declarations: `function snd_ymfpci_create_gameport`, `function snd_ymfpci_free_gameport`, `function snd_ymfpci_create_gameport`, `function snd_ymfpci_free_gameport`, `function snd_card_ymfpci_probe`.
• Atlas domain: Driver Families / sound/pci.
• Implementation status: pattern implementation candidate.

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.