STRUCT DRM_PRIVACY_SCREEN_LOOKUP(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 STRUCT DRM_PRIVACY_SCREEN_LOOKUP(9) 🌸

okay bestie, so this is a page from the Kernel API Manual and it's about struct drm_privacy_screen_lookup β€” yes it's a struct, yes it's in the kernel, and yes we're gonna get through it together πŸ’–


πŸŽ€ NAME πŸŽ€

struct drm_privacy_screen_lookup β€” the static privacy-screen lookup list entry. that's it, that's the whole vibe ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

struct drm_privacy_screen_lookup {
    struct list_head list;
    const char *dev_id;
    const char *con_id;
    const char *provider;
 };

four little fields, all iconic, no notes πŸ’…


πŸ‘‘ Members πŸ‘‘

  • list β€” the lookup list list-entry. literally the little hook that keeps this thing chained into the list 🫢
  • dev_id β€” the consumer device name. or NULL to match all devices β€” yes, all of them, she's not picky 😭
  • con_id β€” the consumer connector name. or NULL to match all connectors. same energy, no cap ⭐
  • provider β€” the dev_name of the privacy_screen provider. that's the one doing the actual providing, main character energy fr fr πŸ”₯

πŸ’œ DESCRIPTION πŸ’œ

so this struct is what powers the static lookup-list β€” the thing that maps privacy-screen consumer dev-connector pairs over to a privacy-screen provider. think of it as the group chat that introduces the consumers to the provider 🌈

it's giving matchmaker, honestly 🧚


⭐ SEE ALSO ⭐

  • Kernel file ./include/drm/drm_privacy_screen_machine.h β€” go read it, bestie, it's right there πŸ™ˆ

πŸ’€ quick reminder: dev_id and con_id are the ones that can be NULL to match everything β€” provider is just the provider's dev_name. don't mix 'em up, iykyk

and that's a wrap, gorgeous πŸ’… this page lives in ./include/drm and it's dated October 2026 β€” so yes, very much the future, we stan a forward-thinking kernel page πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from