drivers/media/platform/renesas/vsp1/vsp1_hgo.h
Source file repositories/reference/linux-study-clean/drivers/media/platform/renesas/vsp1/vsp1_hgo.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/platform/renesas/vsp1/vsp1_hgo.h- Extension
.h- Size
- 898 bytes
- Lines
- 42
- 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.hmedia/v4l2-ctrls.hmedia/v4l2-subdev.hvsp1_histo.h
Detected Declarations
struct vsp1_devicestruct vsp1_hgo
Annotated Snippet
struct vsp1_hgo {
struct vsp1_histogram histo;
struct {
struct v4l2_ctrl_handler handler;
struct v4l2_ctrl *max_rgb;
struct v4l2_ctrl *num_bins;
} ctrls;
bool max_rgb;
unsigned int num_bins;
};
static inline struct vsp1_hgo *to_hgo(struct v4l2_subdev *subdev)
{
return container_of(subdev, struct vsp1_hgo, histo.entity.subdev);
}
struct vsp1_hgo *vsp1_hgo_create(struct vsp1_device *vsp1);
void vsp1_hgo_frame_end(struct vsp1_entity *hgo);
#endif /* __VSP1_HGO_H__ */
Annotation
- Immediate include surface: `media/media-entity.h`, `media/v4l2-ctrls.h`, `media/v4l2-subdev.h`, `vsp1_histo.h`.
- Detected declarations: `struct vsp1_device`, `struct vsp1_hgo`.
- 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.