drivers/media/platform/renesas/vsp1/vsp1_uds.h

File Facts

System

Linux kernel

Corpus path

drivers/media/platform/renesas/vsp1/vsp1_uds.h

Extension

.h

Size

850 bytes

Lines

38

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

• media/media-entity.h
• media/v4l2-subdev.h
• vsp1_entity.h

Detected Declarations

• struct vsp1_device
• struct vsp1_uds

Annotated Snippet

struct vsp1_uds {
	struct vsp1_entity entity;
	bool scale_alpha;
};

static inline struct vsp1_uds *to_uds(struct v4l2_subdev *subdev)
{
	return container_of(subdev, struct vsp1_uds, entity.subdev);
}

struct vsp1_uds *vsp1_uds_create(struct vsp1_device *vsp1, unsigned int index);

void vsp1_uds_set_alpha(struct vsp1_entity *uds, struct vsp1_dl_body *dlb,
			unsigned int alpha);

#endif /* __VSP1_UDS_H__ */

Annotation

• Immediate include surface: `media/media-entity.h`, `media/v4l2-subdev.h`, `vsp1_entity.h`.
• Detected declarations: `struct vsp1_device`, `struct vsp1_uds`.
• 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.