drivers/gpu/drm/xe/xe_reg_whitelist.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/xe/xe_reg_whitelist.h

Extension

.h

Size

523 bytes

Lines

24

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 drm_printer
• struct xe_hw_engine
• struct xe_reg_sr
• struct xe_reg_sr_entry

Annotated Snippet

#ifndef _XE_REG_WHITELIST_H_
#define _XE_REG_WHITELIST_H_

#include <linux/types.h>

struct drm_printer;
struct xe_hw_engine;
struct xe_reg_sr;
struct xe_reg_sr_entry;

void xe_reg_whitelist_process_engine(struct xe_hw_engine *hwe);

void xe_reg_whitelist_print_entry(struct drm_printer *p, unsigned int indent,
				  u32 reg, struct xe_reg_sr_entry *entry);

void xe_reg_whitelist_dump(struct xe_reg_sr *sr, struct drm_printer *p);

#endif

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct drm_printer`, `struct xe_hw_engine`, `struct xe_reg_sr`, `struct xe_reg_sr_entry`.
• 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.