drm_privacy_...tifier_chain(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME 💅

drm_privacy_screen_call_notifier_chain — bestie, this is the little function that tells everybody the privacy screen changed its vibe ✨ (aka notify consumers of state change)

This page is from the Kernel API Manual, and we're gonna get into it 🫶

🌸 SYNOPSIS 🌸

void drm_privacy_screen_call_notifier_chain (struct drm_privacy_screen *priv );

🎀 ARGUMENTS 🎀

  • priv — the privacy screen you're registering the notifier with 💖 (yes, that's literally what it's for)

✨ DESCRIPTION ✨

Okay so picture this: a privacy-screen provider driver can call this function when the privacy-screen state gets changed from the outside. Like, the hardware itself just did its own thing in response to a hotkey press 🔥 — main character energy, honestly.

🚨 The one rule, no cap: this function must be called without holding the privacy-screen lock. Not "maybe," not "if you feel like it." Without. Periodt. 💅

Also, the driver has to update sw_state and hw_state so they actually reflect the new state before it calls this function. Don't skip that step, bestie, it's giving necessary 🔥

So here's the expected behavior from the driver when it receives an external state change event — follow along, it's a whole sequence 🎀:

  1. Take the lock 🔒
  2. Update sw_state and hw_state ✏️
  3. Release the lock 🔓
  4. Call drm_privacy_screen_call_notifier_chain 📣

Like yes, in that order. The lock and unlock are bookends and the state update is the filling. Iconic sandwich behavior, truly.

🦋 SEE ALSO 🦋

That's the whole thing, bestie. This lil page lives in ./drivers/gpu/drm and it's dated October 2026 — so go forth, call your notifier chain, hold zero locks, and slay 🌈👑💜

📦 where this page comes from