drivers/gpu/drm/vboxvideo/hgsmi_channels.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/vboxvideo/hgsmi_channels.h

Extension

.h

Size

1092 bytes

Lines

35

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.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef __HGSMI_CHANNELS_H__
#define __HGSMI_CHANNELS_H__

/*
 * Each channel has an 8 bit identifier. There are a number of predefined
 * (hardcoded) channels.
 *
 * HGSMI_CH_HGSMI channel can be used to map a string channel identifier
 * to a free 16 bit numerical value. values are allocated in range
 * [HGSMI_CH_STRING_FIRST;HGSMI_CH_STRING_LAST].
 */

/* A reserved channel value */
#define HGSMI_CH_RESERVED				0x00
/* HGCMI: setup and configuration */
#define HGSMI_CH_HGSMI					0x01
/* Graphics: VBVA */
#define HGSMI_CH_VBVA					0x02
/* Graphics: Seamless with a single guest region */
#define HGSMI_CH_SEAMLESS				0x03
/* Graphics: Seamless with separate host windows */
#define HGSMI_CH_SEAMLESS2				0x04
/* Graphics: OpenGL HW acceleration */
#define HGSMI_CH_OPENGL					0x05

/* The first channel index to be used for string mappings (inclusive) */
#define HGSMI_CH_STRING_FIRST				0x20
/* The last channel index for string mappings (inclusive) */
#define HGSMI_CH_STRING_LAST				0xff

#endif

Annotation

• 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.