sound/pci/ice1712/prodigy192.h
Source file repositories/reference/linux-study-clean/sound/pci/ice1712/prodigy192.h
File Facts
- System
- Linux kernel
- Corpus path
sound/pci/ice1712/prodigy192.h- Extension
.h- Size
- 715 bytes
- Lines
- 21
- 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_PRODIGY192_H
#define __SOUND_PRODIGY192_H
#define PRODIGY192_DEVICE_DESC "{AudioTrak,Prodigy 192},"
#define PRODIGY192_STAC9460_ADDR 0x54
#define VT1724_SUBDEVICE_PRODIGY192VE 0x34495345 /* PRODIGY 192 VE */
/*
* AudioTrak Prodigy192 GPIO definitions for MI/ODI/O card with
* AK4114 (SPDIF-IN)
*/
#define VT1724_PRODIGY192_CS (1 << 8) /* GPIO8, pin 75 */
#define VT1724_PRODIGY192_CCLK (1 << 9) /* GPIO9, pin 76 */
#define VT1724_PRODIGY192_CDOUT (1 << 10) /* GPIO10, pin 77 */
#define VT1724_PRODIGY192_CDIN (1 << 11) /* GPIO11, pin 86 */
extern struct snd_ice1712_card_info snd_vt1724_prodigy192_cards[];
#endif /* __SOUND_PRODIGY192_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.