drm_plane_force_disable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_plane_force_disable(9) β€” the kernel API manual, but make it make sense

okay so bestie, welcome to drm_plane_force_disable(9), a little corner of the Kernel API Manual that's about to become your whole personality. yes we're doing this. let's go πŸŽ€


✨ NAME ✨

drm_plane_force_disable β€” forcibly disable a plane. not "gently encourage." not "ask nicely." forcibly. it's giving main character energy with zero patience πŸ’…


πŸ”₯ SYNOPSIS πŸ”₯

void drm_plane_force_disable (struct drm_plane *plane );

🧚 ARGUMENTS 🧚

  • plane β€” the plane we're disabling. that's her. that's the one. she's getting turned off, no vote in the matter πŸ’€

🌸 DESCRIPTION 🌸

so literally what it says on the tin: it forces the plane to be disabled. no negotiation, no vibes check, just off.

when do we call it? glad you asked, bestie 🫢

  • when the plane's current framebuffer gets destroyed, and
  • when restoring fbdev mode
🚨 okay important warning, do not skip this. this function is not suitable for atomic drivers. why? because it doesn't wire through the lock acquisition context properly, which means it can't handle retries or driver private locks. so like... it's lowkey not built for the atomic lifestyle, no cap.

if you're on an atomic driver and you're reaching for this, what you probably want instead is drm_atomic_helper_disable_plane or drm_atomic_helper_disable_planes_on_crtc. use those. they ate. 🌈


πŸ‘‘ SEE ALSO πŸ‘‘

the whole squad, fr fr:


⭐ that's the whole page, bestie. this one lives at ./drivers/gpu/drm and it's stamped October 2026 β€” so screenshot it, cite it, print it out and tape it to your monitor. iconic behavior only. mwah πŸ’–πŸ¦‹βœ¨

πŸ“¦ where this page comes from