drivers/media/test-drivers/vivid/vivid-rds-gen.h
Source file repositories/reference/linux-study-clean/drivers/media/test-drivers/vivid/vivid-rds-gen.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/test-drivers/vivid/vivid-rds-gen.h- Extension
.h- Size
- 1220 bytes
- Lines
- 43
- 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
- No C-style include directives detected by the generator.
Detected Declarations
struct vivid_rds_gen
Annotated Snippet
struct vivid_rds_gen {
struct v4l2_rds_data data[VIVID_RDS_GEN_BLOCKS];
bool use_rbds;
u16 picode;
u8 pty;
bool mono_stereo;
bool art_head;
bool compressed;
bool dyn_pty;
bool ta;
bool tp;
bool ms;
char psname[8 + 1];
char radiotext[64 + 1];
};
void vivid_rds_gen_fill(struct vivid_rds_gen *rds, unsigned freq,
bool use_alternate);
void vivid_rds_generate(struct vivid_rds_gen *rds);
#endif
Annotation
- Detected declarations: `struct vivid_rds_gen`.
- 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.