drivers/media/radio/radio-aztech.c

File Facts

System

Linux kernel

Corpus path

drivers/media/radio/radio-aztech.c

Extension

.c

Size

4327 bytes

Lines

162

Domain

Driver Families

Bucket

drivers/media

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• linux/init.h
• linux/ioport.h
• linux/delay.h
• linux/videodev2.h
• linux/io.h
• linux/slab.h
• media/v4l2-device.h
• media/v4l2-ioctl.h
• media/v4l2-ctrls.h
• radio-isa.h
• lm7000.h

Detected Declarations

• struct aztech
• function aztech_set_pins
• function aztech_s_frequency
• function aztech_g_rxsubchans
• function aztech_g_signal
• function aztech_s_mute_volume
• function aztech_init
• function aztech_exit
• module init aztech_init

Annotated Snippet

module_init(aztech_init);
module_exit(aztech_exit);

Annotation

• Immediate include surface: `linux/module.h`, `linux/init.h`, `linux/ioport.h`, `linux/delay.h`, `linux/videodev2.h`, `linux/io.h`, `linux/slab.h`, `media/v4l2-device.h`.
• Detected declarations: `struct aztech`, `function aztech_set_pins`, `function aztech_s_frequency`, `function aztech_g_rxsubchans`, `function aztech_g_signal`, `function aztech_s_mute_volume`, `function aztech_init`, `function aztech_exit`, `module init aztech_init`.
• Atlas domain: Driver Families / drivers/media.
• Implementation status: integration 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.