ssam_ssh_event_enable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

hey bestie 🌸 you're reading ssam_ssh_event_enable(9) from the Kernel API Manual, and we're about to make kernel event enabling feel like a group-chat recap. it's giving "small wrapper, big responsibilities" ✨

πŸ¦‹ NAME πŸ¦‹

ssam_ssh_event_enable - Enable SSH event.

⭐ SYNOPSIS ⭐

int ssam_ssh_event_enable (struct ssam_controller *ctrl , struct
       ssam_event_registry reg , struct ssam_event_id id , u8 flags );

πŸŽ€ ARGUMENTS πŸŽ€

  • ctrl β€” The controller for which to enable the event. like, whose event are we turning on? this one πŸ’…
  • reg β€” The event registry describing what request to use for enabling and disabling the event. she's the blueprint for the enable/disable request, iykyk.
  • id β€” The event identifier. the event's name tag, basically.
  • flags β€” The event flags. the little extra vibes attached to the event.

πŸ’– DESCRIPTION πŸ’–

okay so this one enables the specified event on the EC. periodt.

This function does not manage reference counting of enabled events, and it is basically only a wrapper for the raw EC request. so don't expect her to keep a guest list or count how many times you enabled something β€” she's not doing that, bestie.

If the specified event is already enabled, the EC will ignore this request. no drama, no duplicate enable, the EC just side-eyes it and moves on πŸ™ˆ.

🌈 RETURN 🌈

Returns the status of the executed SAM request (zero on success and negative on direct failure) or -EPROTO if the request response indicates a failure. that's the whole vibe check: zero = slay, negative = something went sideways, and -EPROTO = the response said failure in its little protocol way πŸ’€.

✨ SEE ALSO ✨

the whole related-pages squad, no cap:


okay that's the whole page πŸ’… source/version: ./drivers/platform/surface/agg...; date: October 2026; page: ssam_ssh_event_enable(9). bye bestie, go enable some events 🫢✨

πŸ“¦ where this page comes from