drivers/media/pci/mantis/mantis_vp1041.h
Source file repositories/reference/linux-study-clean/drivers/media/pci/mantis/mantis_vp1041.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/pci/mantis/mantis_vp1041.h- Extension
.h- Size
- 424 bytes
- Lines
- 22
- Domain
- Driver Families
- Bucket
- drivers/media
- 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
mantis_common.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
Mantis VP-1041 driver
Copyright (C) Manu Abraham (abraham.manu@gmail.com)
*/
#ifndef __MANTIS_VP1041_H
#define __MANTIS_VP1041_H
#include "mantis_common.h"
#define MANTIS_VP_1041_DVB_S2 0x0031
#define SKYSTAR_HD2_10 0x0001
#define SKYSTAR_HD2_20 0x0003
#define CINERGY_S2_PCI_HD 0x1179
extern struct mantis_hwconfig vp1041_config;
#endif /* __MANTIS_VP1041_H */
Annotation
- Immediate include surface: `mantis_common.h`.
- Atlas domain: Driver Families / drivers/media.
- 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.