drm_privacy_...en_get_state(9)
π 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 π
- Kernel file
./drivers/gpu/drm/drm_privacy_screen.coverview(9)π drm_privacy_screen_lookup_add(9)drm_privacy_screen_lookup_remove(9)drm_privacy_screen_get(9)drm_privacy_screen_put(9)drm_privacy_screen_set_sw_state(9)drm_privacy_screen_register_notifier(9)drm_privacy_screen_unregister_notifier(9)drm_privacy_screen_register(9)drm_privacy_screen_unregister(9)drm_privacy_screen_call_notifier_chain(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms