dpu_crtc_check_mode_changed(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dpu_crtc_check_mode_changed(9) — from the Kernel API Manual, bestie ✨

Okay so this one is from the Kernel API Manual (yes, the (9) section, we love a kernel-internals moment 👑) and it's genuinely so useful — it's the little function that answers the question everyone asks before a big change: do we need to redo the whole modeset, or are we fine? 🦋

🌸 NAME 🌸

dpu_crtc_check_mode_changed — literally just checking if a full modeset is required, no cap 💅

✨ SYNOPSIS ✨

int dpu_crtc_check_mode_changed (struct drm_crtc_state *old_crtc_state ,
struct drm_crtc_state *new_crtc_state );

So it takes two states and gives you back an int — that's the whole vibe check in one line 🫶

🎀 ARGUMENTS 🎀

  • old_crtc_state — the previous CRTC state, aka the "before" pic 📸
  • new_crtc_state — the corresponding CRTC state that's gonna get checked, aka the "after" pic 🪞

Two states, one comparison, we're so back 😭

🔥 DESCRIPTION 🔥

The way this function's whole job is to check if the changes in the object properties demand full mode set — that's it, that's the function 💀 It looks at what changed between those two states and tells you whether the properties shifted enough that a full modeset is required. Not a partial thing, not a "eh, close enough" thing — full mode set. Periodt 💅

🌈 SEE ALSO 🌈

Kernel file: ./drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c — the main character file itself, go read it iykyk 📖

And the whole friend group 💖:

Squad goals, fr fr 🧚

Quick reminder bestie: this one's only a check — it tells you if a full modeset is required, it doesn't do the whole thing for you 🙈

Alright that's the page! Source/version biz: this lives over in ./drivers/gpu/drm/msm/disp/dpu1, and it's dated October 2026 — so go forth, check those mode changes, and slay 💅✨🍓

📦 where this page comes from