xe_pcode_ready(9)

✨ NAME ✨

okay so bestie, this is xe_pcode_ready(9) from the Kernel API Manual, and its whole mission is literally: ensure PCODE is initialized. that's the name, that's the vibe, no cap 💅

🌸 SYNOPSIS 🌸

int xe_pcode_ready (struct xe_device *xe , bool locked );

🎀 ARGUMENTS 🎀

• xe — xe instance. like, the xe instance itself 🫶
• locked — true if lock held, false otherwise. yes bestie, it's a bool situation 💅

🦋 DESCRIPTION 🦋

okay so here's the tea ☕ — the PCODE init mailbox is polled only on root gt of root tile, because the root tile provides the initialization is complete only after all the tiles have completed the initialization. literally all the tiles gotta finish before it's official, periodt 💖

it's called only on early probe without locks, and with locks in resume path. so yeah, both modes are a whole thing ✨

and the return vibes? it returns 0 on success, and -error number on failure. that's it, that's the whole mood 🫶

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/xe/xe_pcode.c
• PCODE(9)
• xe_pcode_request(9)
• xe_pcode_init_min_freq_table(9)
• xe_pcode_init_early(9)
• xe_pcode_probe_early(9)
• xe_get_pcode_version(9)

mwah 💋 — source/version cutie lives under ./drivers/gpu/drm/xe, dated October 2026, and it's literally xe_pcode_ready(9). periodt 🫶