drivers/media/pci/netup_unidvb/netup_unidvb_core.c

File Facts

System

Linux kernel

Corpus path

drivers/media/pci/netup_unidvb/netup_unidvb_core.c

Extension

.c

Size

30085 bytes

Lines

1029

Domain

Driver Families

Bucket

drivers/media

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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 an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• 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/init.h
• linux/module.h
• linux/moduleparam.h
• linux/kmod.h
• linux/kernel.h
• linux/slab.h
• linux/interrupt.h
• linux/delay.h
• linux/list.h
• media/videobuf2-v4l2.h
• media/videobuf2-vmalloc.h
• netup_unidvb.h
• cxd2841er.h
• horus3a.h
• ascot2e.h
• helene.h
• lnbh25.h

Detected Declarations

• struct netup_dma_regs
• struct netup_unidvb_buffer
• function netup_unidvb_tuner_ctrl
• function netup_unidvb_dev_enable
• function netup_unidvb_dma_enable
• function netup_dma_interrupt
• function netup_unidvb_isr
• function netup_unidvb_queue_setup
• function netup_unidvb_buf_prepare
• function netup_unidvb_buf_queue
• function netup_unidvb_start_streaming
• function netup_unidvb_stop_streaming
• function netup_unidvb_queue_init
• function netup_unidvb_dvb_init
• function netup_unidvb_dvb_fini
• function netup_unidvb_dvb_setup
• function netup_unidvb_ring_copy
• function netup_unidvb_dma_worker
• function netup_unidvb_queue_cleanup
• function netup_unidvb_dma_timeout
• function netup_unidvb_dma_init
• function netup_unidvb_dma_fini
• function netup_unidvb_dma_setup
• function netup_unidvb_ci_setup
• function netup_unidvb_request_mmio
• function pci_resource_len
• function netup_unidvb_request_modules
• function netup_unidvb_initdev
• function netup_unidvb_finidev

Annotated Snippet

static struct pci_driver netup_unidvb_pci_driver = {
	.name     = "netup_unidvb",
	.id_table = netup_unidvb_pci_tbl,
	.probe    = netup_unidvb_initdev,
	.remove   = netup_unidvb_finidev,
};

module_pci_driver(netup_unidvb_pci_driver);

Annotation

• Immediate include surface: `linux/init.h`, `linux/module.h`, `linux/moduleparam.h`, `linux/kmod.h`, `linux/kernel.h`, `linux/slab.h`, `linux/interrupt.h`, `linux/delay.h`.
• Detected declarations: `struct netup_dma_regs`, `struct netup_unidvb_buffer`, `function netup_unidvb_tuner_ctrl`, `function netup_unidvb_dev_enable`, `function netup_unidvb_dma_enable`, `function netup_dma_interrupt`, `function netup_unidvb_isr`, `function netup_unidvb_queue_setup`, `function netup_unidvb_buf_prepare`, `function netup_unidvb_buf_queue`.
• Atlas domain: Driver Families / drivers/media.
• Implementation status: pattern implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.