drm_privacy_screen_get(9)

💅 drm_privacy_screen_get(9) — from the Kernel API Manual, bestie 🎀

okay so picture this: you're a driver, you've got a display, and that display has a little privacy screen attached (yes, the fancy one that fogs up so nobody can peek at your screen on the train 🚄). This function is literally how you go get the provider for it. main character energy only ✨

---

🌸 NAME 🌸

drm_privacy_screen_get — get a privacy-screen provider 🫶

---

✨ SYNOPSIS ✨

struct drm_privacy_screen * drm_privacy_screen_get (struct device *dev ,
const char *con_id );

---

🎀 ARGUMENTS 🎀

• dev — the consumer-device, aka the one that's asking for a privacy-screen provider. it's giving "hi, do you have one for me?" 💁‍♀️
• con_id — the (video)connector name you want the privacy-screen provider for. this is the specific connector you're matching against, no cap 🔍

---

💖 DESCRIPTION 💖

So the whole vibe: you call this and it gets you a privacy-screen provider for a privacy-screen that's attached to the display described by the dev and con_id parameters. that's it, that's the function. simple, iconic, does exactly what it says on the tin 🧚

---

🌈 RETURN 🌈

here's the vibe check on what you get back:

• A pointer to a struct drm_privacy_screen on success. slay, you got one 👑
• ERR_PTR(-ENODEV) if no matching privacy-screen is found. literally nothing matched, tragic 😭
• ERR_PTR(-EPROBE_DEFER) if there is a matching privacy-screen, but it hasn't been registered yet. so it exists, it's just not ready — come back later bestie 🙈

fr fr, check for those ERR_PTR values before you go dereferencing anything. -EPROBE_DEFER especially means "try again", not "give up forever" 💀

---

🌟 SEE ALSO 🌟

the whole friend group, in no particular order:

• Kernel file ./drivers/gpu/drm/drm_privacy_screen.c
• overview(9)
• drm_privacy_screen_lookup_add(9)
• drm_privacy_screen_lookup_remove(9)
• drm_privacy_screen_put(9)
• drm_privacy_screen_set_sw_state(9)
• drm_privacy_screen_get_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 that's the whole page, and yes you read that right — it's from ./drivers/gpu/drm, dated October 2026, so go forth and get yourself a privacy-screen provider 💜✨ periodt.