scmi_get_active_handler(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… scmi_get_active_handler(9) πŸ’…

okay so this one comes straight from the Kernel API Manual, and it's literally a tiny helper doing active-handler business. bestie, it's giving β€œquick lookup, no drama” energy. πŸ¦‹


✨ NAME ✨

scmi_get_active_handler β€” Helper to get active handlers only πŸ’–

🌸 SYNOPSIS 🌸

       struct scmi_event_handler * scmi_get_active_handler (struct
       scmi_notify_instance *ni , u32 evt_key );

πŸŽ€ ARGUMENTS πŸŽ€

  • ni β€” a reference to the notification instance to use. yep, that’s the one you’re handing over 🫢
  • evt_key β€” the event key to use. the key key key πŸ”‘

πŸ’« DESCRIPTION πŸ’«

okay so it searches for the handler you want β€” the one matching the key β€” and it looks only in the per-protocol table of registered handlers. that’s the whole search zone, bestie.

this is called only from the dispatching path, so it wants to be as quick as possible and genuinely does not care about pending. like, no cap, speed is the entire vibe here. periodt. πŸ’…

⭐ RETURN ⭐

A properly refcounted active handler ✨ β€” yes, properly refcounted, we love a responsible icon πŸ‘‘

🌈 SEE ALSO 🌈


this page lives under ./drivers/firmware/arm_scmi, and it’s dated October 2026 β€” mwah πŸ’‹

πŸ“¦ where this page comes from