drivers/staging/media/tegra-video/video.h

File Facts

System

Linux kernel

Corpus path

drivers/staging/media/tegra-video/video.h

Extension

.h

Size

699 bytes

Lines

30

Domain

Driver Families

Bucket

drivers/staging

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

• linux/host1x.h
• media/media-device.h
• media/v4l2-device.h
• vi.h

Detected Declarations

• struct tegra_video_device

Annotated Snippet

struct tegra_video_device {
	struct v4l2_device v4l2_dev;
	struct media_device media_dev;
	struct tegra_vi *vi;
	struct tegra_csi *csi;
};

int tegra_v4l2_nodes_setup_tpg(struct tegra_video_device *vid);
void tegra_v4l2_nodes_cleanup_tpg(struct tegra_video_device *vid);

extern struct platform_driver tegra_vi_driver;
extern struct platform_driver tegra_vip_driver;
extern struct platform_driver tegra_csi_driver;
#endif

Annotation

• Immediate include surface: `linux/host1x.h`, `media/media-device.h`, `media/v4l2-device.h`, `vi.h`.
• Detected declarations: `struct tegra_video_device`.
• Atlas domain: Driver Families / drivers/staging.
• 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.