drivers/media/usb/pvrusb2/pvrusb2-main.c

File Facts

System

Linux kernel

Corpus path

drivers/media/usb/pvrusb2/pvrusb2-main.c

Extension

.c

Size

3145 bytes

Lines

146

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kernel.h
• linux/errno.h
• linux/module.h
• linux/usb.h
• linux/videodev2.h
• pvrusb2-hdw.h
• pvrusb2-devattr.h
• pvrusb2-context.h
• pvrusb2-debug.h
• pvrusb2-v4l2.h
• pvrusb2-sysfs.h

Detected Declarations

• function pvr_setup_attach
• function pvr_probe
• function pvr_disconnect
• function pvr_init
• function pvr_exit
• module init pvr_init

Annotated Snippet

module_init(pvr_init);
module_exit(pvr_exit);

MODULE_AUTHOR(DRIVER_AUTHOR);
MODULE_DESCRIPTION(DRIVER_DESC);
MODULE_LICENSE("GPL");
MODULE_VERSION("0.9.1");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/errno.h`, `linux/module.h`, `linux/usb.h`, `linux/videodev2.h`, `pvrusb2-hdw.h`, `pvrusb2-devattr.h`, `pvrusb2-context.h`.
• Detected declarations: `function pvr_setup_attach`, `function pvr_probe`, `function pvr_disconnect`, `function pvr_init`, `function pvr_exit`, `module init pvr_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.