drivers/gpu/drm/vboxvideo/hgsmi_ch_setup.h
Source file repositories/reference/linux-study-clean/drivers/gpu/drm/vboxvideo/hgsmi_ch_setup.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/gpu/drm/vboxvideo/hgsmi_ch_setup.h- Extension
.h- Size
- 853 bytes
- Lines
- 33
- Domain
- Driver Families
- Bucket
- drivers/gpu
- 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
- No C-style include directives detected by the generator.
Detected Declarations
struct hgsmi_buffer_locationstruct hgsmi_host_flags
Annotated Snippet
struct hgsmi_buffer_location {
u32 buf_location;
u32 buf_len;
} __packed;
/* HGSMI setup and configuration data structures. */
#define HGSMIHOSTFLAGS_COMMANDS_PENDING 0x01u
#define HGSMIHOSTFLAGS_IRQ 0x02u
#define HGSMIHOSTFLAGS_VSYNC 0x10u
#define HGSMIHOSTFLAGS_HOTPLUG 0x20u
#define HGSMIHOSTFLAGS_CURSOR_CAPABILITIES 0x40u
struct hgsmi_host_flags {
u32 host_flags;
u32 reserved[3];
} __packed;
#endif
Annotation
- Detected declarations: `struct hgsmi_buffer_location`, `struct hgsmi_host_flags`.
- Atlas domain: Driver Families / drivers/gpu.
- 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.