intel_displ...river_remove(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… intel_displ...river_remove(9) β€” like, the Kernel API Manual one πŸŽ€

okay bestie so this is a kernel API manual page (that's the manual name, keep up ✨) and it's about deinitializing hw power domain state. ngl it sounds scary but it's literally just cleanup duty. let's go πŸ¦‹


✨ NAME ✨

intel_display_power_driver_remove β€” the one that deinitializes hw power domain state 🧚


πŸ”₯ SYNOPSIS πŸ”₯

void intel_display_power_driver_remove (struct intel_display *display );

like, that's the whole vibe. one function, one pointer, done πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • display β€” the display device instance πŸ–₯️ that's it, that's the entire arg list, she's low maintenance

🌸 DESCRIPTION 🌸

So intel_display_power_driver_remove de-initializes the display power domain HW state. it's giving janitor energy but make it iconic β€” it's tearing down the HW state and wrapping things up ✨

it also makes sure the device stays powered up so that the driver can be reloaded. like it's holding the door open for the driver to come back in later, no cap 🫢

⚠️ okay this part is important bestie, read it twice: it must be called with power domains already disabled (after a call to intel_display_power_disable) and it must be paired with intel_display_power_init_hw. not optional. the power domain situationship has rules πŸ’€

πŸ’œ SEE ALSO πŸ’œ

this is the friend group, the whole crew ykyk 🌈


okay and for the lil sign-off 🫢 this whole thing lives under ./drivers/gpu/drm/i915/display, it's dated October 2026 (yes future queen πŸ’«), and it's from the Kernel API Manual obvs. k byeee, go disable those power domains before you call her πŸ’–πŸ‘‘

πŸ“¦ where this page comes from