sound/pci/ice1712/prodigy_hifi.h

File Facts

System

Linux kernel

Corpus path

sound/pci/ice1712/prodigy_hifi.h

Extension

.h

Size

808 bytes

Lines

25

Domain

Driver Families

Bucket

sound/pci

Inferred role

Driver Families: implementation source

Status

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

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef __SOUND_PRODIGY_HIFI_H
#define __SOUND_PRODIGY_HIFI_H

/*
 *   ALSA driver for VIA VT1724 (Envy24HT)
 *
 *   Lowlevel functions for Audiotrak Prodigy Hifi
 *
 *	Copyright (c) 2004 Takashi Iwai <tiwai@suse.de>
 */      

#define PRODIGY_HIFI_DEVICE_DESC 	       "{Audiotrak,Prodigy 7.1 HIFI},"\
                                           "{Audiotrak Prodigy HD2},"\
                                           "{Hercules Fortissimo IV},"

#define VT1724_SUBDEVICE_PRODIGY_HIFI	0x38315441	/* PRODIGY 7.1 HIFI */
#define VT1724_SUBDEVICE_PRODIGY_HD2	0x37315441	/* PRODIGY HD2 */
#define VT1724_SUBDEVICE_FORTISSIMO4	0x81160100	/* Fortissimo IV */


extern struct snd_ice1712_card_info  snd_vt1724_prodigy_hifi_cards[];

#endif /* __SOUND_PRODIGY_HIFI_H */

Annotation

• Atlas domain: Driver Families / sound/pci.
• Implementation status: source 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.