drm_privacy_...en_get_state(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

okay so bestie, welcome to the drm_privacy_screen_get_state(9) page from the Kernel API Manual β€” yes, that exact manual, and we are literally getting the privacy-screen's current state.

drm_privacy_screen_get_state β€” get privacy-screen's current state 🌸


✨ SYNOPSIS ✨

void drm_privacy_screen_get_state (struct drm_privacy_screen *priv ,
enum drm_privacy_screen_status *sw_state_ret , enum
drm_privacy_screen_status *hw_state_ret );

it's giving void, so no return value is coming back at you β€” the state info goes where the arguments point. πŸ’…


🫢 ARGUMENTS 🫢

  • priv β€” the privacy screen to get the state for. this is the main-character privacy screen, periodt.
  • sw_state_ret β€” address where to store the privacy-screen's current sw-state. yes, the sw-state goes right there.
  • hw_state_ret β€” address where to store the privacy-screen's current hw-state. and the hw-state goes right there too.

πŸ’… DESCRIPTION πŸ’…

Get the current state of a privacy-screen β€” both the sw-state and the hw-state. that's the whole vibe: current state, sw-state, hw-state, both of them, no cap. πŸ”₯

ngl, this one is short and iconic: you hand it a privacy screen, plus places to store the current sw-state and hw-state, and it gets the current state of that privacy-screen. πŸ¦‹


🌈 SEE ALSO 🌈


okay byeee 🫢 this page is from ./drivers/gpu/drm, October 2026, and the footer name is drm_privacy_...en_get_state(9) β€” slay, go get that state bestie πŸ’–βœ¨

πŸ“¦ where this page comes from