drivers/gpu/drm/xe/regs/xe_pmt.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/xe/regs/xe_pmt.h

Extension

.h

Size

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

Dependency Surface

• xe_regs.h

Detected Declarations

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

Annotated Snippet

#ifndef _XE_PMT_H_
#define _XE_PMT_H_

#include "xe_regs.h"

#define BMG_PMT_BASE_OFFSET		0xDB000
#define BMG_DISCOVERY_OFFSET		(SOC_BASE + BMG_PMT_BASE_OFFSET)

#define PUNIT_TELEMETRY_GUID		XE_REG(BMG_DISCOVERY_OFFSET + 0x4)
#define BMG_ENERGY_STATUS_PMT_OFFSET	(0x30)
#define	ENERGY_PKG			REG_GENMASK64(31, 0)
#define	ENERGY_CARD			REG_GENMASK64(63, 32)

#define BMG_TELEMETRY_BASE_OFFSET	0xE0000
#define BMG_TELEMETRY_OFFSET		(SOC_BASE + BMG_TELEMETRY_BASE_OFFSET)

#define BMG_MODS_RESIDENCY_OFFSET		(0x4D0)
#define BMG_G2_RESIDENCY_OFFSET		(0x530)
#define BMG_G6_RESIDENCY_OFFSET		(0x538)
#define BMG_G7_RESIDENCY_OFFSET		(0x4B0)
#define BMG_G8_RESIDENCY_OFFSET		(0x540)
#define BMG_G10_RESIDENCY_OFFSET		(0x548)

#define BMG_PCIE_LINK_L0_RESIDENCY_OFFSET	(0x570)
#define BMG_PCIE_LINK_L1_RESIDENCY_OFFSET	(0x578)
#define BMG_PCIE_LINK_L1_2_RESIDENCY_OFFSET	(0x580)

#endif

Annotation

• Immediate include surface: `xe_regs.h`.
• 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.