ssam_device...r_unregister(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so this is ssam_device_notifier_unregister β€” the header calls the page ssam_device...r_unregister(9), and it lives in the Kernel API Manual, bestie. Its whole job is literally: unregister an event notifier for the specified client device. periodt. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

int ssam_device_notifier_unregister (struct ssam_device *sdev , struct ssam_event_notifier *n );

✨ ARGUMENTS ✨

  • sdev β€” the device the notifier has been registered on. (like, the home base for this notifier 🫢)
  • n β€” the event notifier to unregister. (the one getting its goodbye moment πŸ‘‹)

πŸ’– DESCRIPTION πŸ’–

Unregister an event notifier. Decrement the usage counter of the associated SAM event if the notifier is not marked as an observer. If the usage counter reaches zero, the event will be disabled. no cap, that counter matters ✨

In case the device has been marked as hot-removed, the event will not be disabled on the EC, as in those cases any attempt at doing so may time out. so yeah, hands off the EC in that situation, fr fr 😭

πŸŽ€ RETURN πŸŽ€

Returns zero on success, -ENOENT if the given notifier block has not been registered on the controller. If the given notifier block was the last one associated with its specific event, returns the status of the event-disable EC-command. like, every possible outcome is right there, iykyk 🌈

🌈 SEE ALSO 🌈

all the cross-refs, no skipping, no cap:


okay bye bestie πŸ’–βœ¨ this page came from ./include/linux/surface_aggreg..., dated October 2026, and it’s literally ssam_device...r_unregister(9) signing off πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from