ssam_notifier_unregister(9)

💅 ssam_notifier_unregister(9) — Kernel API Manual ✨

okay bestie, so this is a kernel API manual page, and it's about ssam_notifier_unregister(9) — the function that takes an event notifier off a Surface Aggregator controller. It's giving cleanup era and honestly it's lowkey iconic. 🎀

---

🌸 NAME 🌸

ssam_notifier_unregister — unregister an event notifier. literally what it says on the tin, no cap. 💖

---

✨ SYNOPSIS ✨

int ssam_notifier_unregister (struct ssam_controller *ctrl , struct
       ssam_event_notifier *n );

two args, one int back, periodt. 🫶

---

🦋 ARGUMENTS 🦋

• ctrl — the controller the notifier has been registered on. like, the one it's currently in a situationship with. you gotta name it or the unregistration won't know where to happen 💀
• n — the event notifier to unregister. this is the one getting the ✨ it's not you it's me ✨ talk.

---

🔥 DESCRIPTION 🔥

so you're unregistering an event notifier. slay. here's the tea though, and it's important tea:

the function decrements the usage counter of the associated SAM event — but ONLY if the notifier is not marked as an observer. if it is an observer, no counter decrementing happens. iykyk. 👀

and then, if the usage counter reaches zero? the event gets disabled. gone. powered down. the whole vibe check failed and the event left the chat. 😭

---

👑 RETURN 👑

Returns zero on success — bestie behaviour, we love to see it 💅. plus:

• -ENOENT — if the given notifier block has not been registered on the controller. awkward. you can't break up with someone you were never dating, bestie 🙈
• If the given notifier block was the last one associated with its specific event, it returns the status of the event-disable EC-command. so whatever that EC-command says, that's what you get. main character return value energy fr fr ⭐

---

🌈 SEE ALSO 🌈

okay this list is LONG and we are NOT skipping any of it, because every single one of these is a friend of the family:

Kernel file ./include/linux/surface_aggregator/controller.h — that's the file, keep it exactly like that 🧚

then the crew:

• enum ssam_event_flags(9)
• struct ssam_event(9)
• enum ssam_request_flags(9)
• struct ssam_request(9)
• struct ssam_response(9)
• struct ssam_request_sync(9)
• ssam_request_sync_set_data(9)
• ssam_request_sync_set_resp(9)
• ssam_request_sync_wait(9)
• ssam_request_do_sync_onstack(9)
• __ssam_retry(9)
• ssam_retry(9)
• struct ssam_request_spec(9)
• struct ssam_request_spec_md(9)
• SSAM_DEFINE_SYNC_REQUEST_N(9)
• SSAM_DEFINE_SYNC_REQUEST_W(9)
• SSAM_DEFINE_SYNC_REQUEST_R(9)
• SSAM_DEFINE_SYNC_REQUEST_WR(9)
• SSAM_DEFINE_SYNC_REQUEST_MD_N(9)
• SSAM_DEFINE_SYNC_REQUEST_MD_W(9)
• SSAM_DEFINE_SYNC_REQUEST_MD_R(9)
• SSAM_DEFINE_SYNC_REQUEST_MD_WR(9)
• enum ssam_notif_flags(9)
• struct ssam_notifier_block(9)
• ssam_notifier_from_errno(9)
• ssam_notifier_to_errno(9)
• struct ssam_event_registry(9)
• struct ssam_event_id(9)
• enum ssam_event_mask(9)
• SSAM_EVENT_REGISTRY(9)
• enum ssam_event_notifier_flags(9)
• struct ssam_event_notifier(9)

see? told you we weren't skipping any. ate and left no crumbs 🍓

---

💀 quick vibe check reminder: if the notifier is marked as an observer, the usage counter does not get decremented — that's straight from the description, don't @ me.

---

and that's the whole page, bestie! this came from the kernel source tree at ./include/linux/surface_aggreg... and it's dated October 2026 — so yeah, future vibes ✨🦋. go forth and unregister responsibly. 💜🎀