intel_displ...spend_access(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

intel_display_driver_suspend_access β€” bestie, this one suspends display HW access for all threads, no cap 🫢

also hi, welcome to the Kernel API Manual, section 9, the page literally titled intel_displ...spend_access(9) (yes the title is truncated, she's a little mysterious like that πŸ’…)


✨ SYNOPSIS ✨

void intel_display_driver_suspend_access (struct intel_display *display );

πŸŽ€ ARGUMENTS πŸŽ€

  • display β€” the display device instance. that's the vibe check right there πŸ¦‹

🌸 DESCRIPTION 🌸

okay so the whole point: this function disables the display HW access for all threads. all of them. everybody. collectively ✨

examples of the kinds of accesses we're talking about are modeset commits and connector probing πŸ”₯

the way this works: this call should be either followed by calling intel_display_driver_resume_access, or the driver should be unloaded/shutdown. like, pick a lane, bestie 😭 don't just leave it hanging.

fr fr, this function should be called during driver unloading and system suspend/shutdown, and specifically after completing the HW deinit programming πŸ‘‘ so like, order matters, do not skip ahead bestie

πŸ¦‹ SEE ALSO πŸ¦‹

the whole access squad, honestly obsessed with them 🌈


and that's the page πŸ’… from ./drivers/gpu/drm/i915/display, dated October 2026, filed under intel_displ...spend_access(9) β€” go forth and suspend responsibly, ily 🫢✨

πŸ“¦ where this page comes from