DPU_DEBUG(9)
π DPU_DEBUG(9) π
okay so this is a page from the Kernel API Manual β yes bestie, the kernel has lore too β and it's all about DPU_DEBUG, the macro that handles your kms/plane/crtc/encoder/connector logs. it's giving "logging but make it DRM-coded" β¨
πΈ NAME πΈ
DPU_DEBUG β the macro for kms/plane/crtc/encoder/connector logs π«Ά
like, that's literally its whole job. one macro, five whole categories of display pipeline things to log about. she's versatile. she's employed. we love her π
β SYNOPSIS β
DPU_DEBUG (fmt , ... );
that's it. that's the whole vibe check. fmt, then your little trail of ... besties trailing behind it π
π¦ ARGUMENTS π¦
fmtβ a pointer to the format string π like, the blueprint of the message, the main character of the call, the outline before the glow-up...β variable arguments π the supporting cast! however many you need, they just keep coming, no cap
no cap:fmtis a pointer to a format string, and...is variable arguments. don't come for me, that's exactly what the page says π
π₯ SEE ALSO π₯
- the kernel file
./drivers/gpu/drm/msm/disp/dpu1/dpu_kms.hβ go read the source, iykyk π DPU_DEBUG_DRIVER(9)β her sibling, also iconicktime_compare_safe(9)β time comparison, but safe, and honestly? slay
and that's the whole page!! short and sweet, just like a good group chat message π
source: ./drivers/gpu/drm/msm/disp/dpu1 πΈ dated October 2026, so likeβ¦ future era. mark your calendars bestie π
π bye, ily, go log something π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms