drivers/gpu/drm/xe/abi/guc_lic_abi.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/xe/abi/guc_lic_abi.h

Extension

.h

Size

2041 bytes

Lines

78

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

• linux/types.h

Detected Declarations

• struct guc_lic
• enum guc_lic_type

Annotated Snippet

struct guc_lic {
	/**
	 * @magic: A magic number set by GuC to identify that this
	 * structure contains valid information: magic = GUC_LIC_MAGIC.
	 */
	u32 magic;
#define GUC_LIC_MAGIC			0x8086900D
	/**
	 * @version: The version of the this structure.
	 * Major and minor version number are represented as bit fields.
	 */
	u32 version;
#define GUC_LIC_VERSION_MASK_MAJOR		GENMASK(31, 16)
#define GUC_LIC_VERSION_MASK_MINOR		GENMASK(15, 0)

#define GUC_LIC_VERSION_MAJOR	1u
#define GUC_LIC_VERSION_MINOR	0u

	/** @data_count: Number of dwords the `data` array contains. */
	u32 data_count;
	/**
	 * @data: Array of dwords representing a list of LIC KLVs of
	 * type guc_klv_generic with keys represented by guc_lic_type
	 */
	u32 data[] __counted_by(data_count);
} __packed;

#endif

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct guc_lic`, `enum guc_lic_type`.
• 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.