intel_frontb...r_invalidate(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… intel_frontbuffer_invalidate β€” invalidate frontbuffer object

okay so bestie, we're in the Kernel API Manual today and the star of the show is intel_frontbuffer_invalidate πŸ’– (the header truncates it all cute like intel_frontb...r_invalidate(9), but you and me both know the whole name, iykyk ✨)


🌸 SYNOPSIS 🌸

bool intel_frontbuffer_invalidate (struct intel_frontbuffer *front ,
       enum fb_op_origin origin );

like, that's the whole vibe check β€” two args, one bool coming back atcha 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • front β€” the GEM object we're invalidating, bestie. that's the main character right there πŸ‘‘
  • origin β€” which operation caused the invalidation. literally the receipts of why this is happening πŸ”₯

πŸ¦‹ DESCRIPTION πŸ¦‹

so this function gets called every single time rendering on the given object starts, and frontbuffer caching has gotta get invalidated β€” we're talking fbc, low refresh rate for DRRS, and panel self refresh. all three, no cap πŸ’…

and here's the tea for ORIGIN_CS specifically β˜• β€” any subsequent invalidation gets delayed until the rendering completes, or until a flip on this frontbuffer plane is scheduled. so like... it waits its turn, periodt ✨

ngl this one's important β€” if you skip the invalidate, your cached frontbuffer is just sitting there lying to you πŸ’€

🌈 SEE ALSO 🌈

  • Kernel file ./drivers/gpu/drm/i915/display/intel_frontbuffer.h β€” go read the header, it's giving source of truth πŸ“–
  • intel_frontbuffer_flush(9) β€” the sibling function, obvi 🧚

okay that's the whole page, mwah πŸ’œ this little masterpiece lives in ./drivers/gpu/drm/i915/display and it's dated October 2026, so like, future vibes only ⭐ slay, go invalidate something responsibly πŸŽ€

πŸ“¦ where this page comes from