XE_REG_INITIALIZER(9)

💅 XE_REG_INITIALIZER(9) — like, the kernel API manual bestie ✨

okay so this is a page from the Kernel API Manual and it's all about XE_REG_INITIALIZER, which is genuinely the moment you need when you're stuck initializing a xe_reg_t in a place where you literally cannot do the fun stuff. no cap, it's niche but it's iconic 🎀

---

🌸 NAME 🌸

XE_REG_INITIALIZER — the initializer for xe_reg_t. that's it, that's the whole vibe. 💅

---

✨ SYNOPSIS ✨

XE_REG_INITIALIZER (r_ , ... );

look at her go 🦋

---

🎀 ARGUMENTS 🎀

• r_ — the register offset. this one is the whole point, bestie, it's mandatory 👑
• ... — additional options, like access mode and whatever else. peek at struct xe_reg for the available options, iykyk 🔥

---

💖 DESCRIPTION 💖

so here's the tea: the register field is mandatory, and then any additional options get passed along as arguments after it. simple, slay 🌈

usually you'd reach for XE_REG instead, because it creates an object of the right type — that's the main character energy move and generally what you should prefer. ✨

but — and this is the plot twist 😭 — when you're initializing static const storage, where a compound statement is not allowed, you can use this instead. it's giving "the backup plan that eats every time" 🍓

lowkey important: the compound-statement restriction is the whole reason this exists, so don't come for XE_REG's gig unless you're literally in that static const situation 💀

---

🫶 SEE ALSO 🫶

• Kernel file ./drivers/gpu/drm/xe/regs/xe_reg_defs.h
• XE_REG_ADDR_MAX(9)
• struct xe_reg(9)
• struct xe_reg_mcr(9)
• XE_REG_OPTION_MASKED(9)
• XE_REG_OPTION_VF(9)
• XE_REG(9)
• XE_REG_MCR(9)

go read all of them, fr fr, they're all connected and it's a whole lore drop 🧚💜

---

⭐ this little masterpiece lives over in ./drivers/gpu/drm/xe/regs and it's dated October 2026 — mwah, take care of her, bye bestie! 🙈💖