drivers/media/test-drivers/vivid/vivid-radio-common.h

File Facts

System

Linux kernel

Corpus path

drivers/media/test-drivers/vivid/vivid-radio-common.h

Extension

.h

Size

966 bytes

Lines

29

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

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

Annotated Snippet

#ifndef _VIVID_RADIO_COMMON_H_
#define _VIVID_RADIO_COMMON_H_

/* The supported radio frequency ranges in kHz */
#define FM_FREQ_RANGE_LOW       (64000U * 16U)
#define FM_FREQ_RANGE_HIGH      (108000U * 16U)
#define AM_FREQ_RANGE_LOW       (520U * 16U)
#define AM_FREQ_RANGE_HIGH      (1710U * 16U)
#define SW_FREQ_RANGE_LOW       (2300U * 16U)
#define SW_FREQ_RANGE_HIGH      (26100U * 16U)

enum { BAND_FM, BAND_AM, BAND_SW, TOT_BANDS };

extern const struct v4l2_frequency_band vivid_radio_bands[TOT_BANDS];

int vivid_radio_g_frequency(struct file *file, const unsigned *freq, struct v4l2_frequency *vf);
int vivid_radio_s_frequency(struct file *file, unsigned *freq, const struct v4l2_frequency *vf);

void vivid_radio_rds_init(struct vivid_dev *dev);

#endif

Annotation

• 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.