ssam_ssh_event_enable(9)
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:
- Kernel file:
./drivers/platform/surface/aggregator/controller.c ssh_seq_reset(9)ssh_seq_next(9)ssh_rqid_reset(9)ssh_rqid_next(9)ssam_event_matches_notifier(9)ssam_nfblk_call_chain(9)ssam_nfblk_insert(9)ssam_nfblk_find(9)ssam_nfblk_remove(9)ssam_nf_head_init(9)ssam_nf_head_destroy(9)struct ssam_nf_refcount_key(9)struct ssam_nf_refcount_entry(9)ssam_nf_refcount_inc(9)ssam_nf_refcount_dec(9)ssam_nf_refcount_dec_free(9)ssam_nf_refcount_empty(9)ssam_nf_call(9)ssam_nf_init(9)ssam_nf_destroy(9)ssam_event_item_cache_init(9)ssam_event_item_cache_destroy(9)ssam_event_item_free(9)ssam_event_item_alloc(9)ssam_event_queue_push(9)ssam_event_queue_pop(9)ssam_event_queue_is_empty(9)ssam_cplt_get_event_queue(9)ssam_cplt_submit(9)ssam_cplt_submit_event(9)ssam_cplt_flush(9)ssam_event_queue_init(9)ssam_cplt_init(9)ssam_cplt_destroy(9)ssam_controller_device(9)ssam_controller_get(9)ssam_controller_put(9)ssam_controller_statelock(9)ssam_controller_stateunlock(9)ssam_controller_lock(9)ssam_controller_caps_load_from_acpi(9)ssam_controller_caps_load_from_of(9)ssam_controller_caps_load(9)ssam_controller_init(9)ssam_controller_start(9)ssam_controller_shutdown(9)ssam_controller_destroy(9)ssam_controller_suspend(9)ssam_controller_resume(9)ssam_request_write_data(9)ssam_request_sync_alloc(9)ssam_request_sync_free(9)ssam_request_sync_init(9)ssam_request_sync_submit(9)ssam_request_do_sync(9)ssam_request_do_sync_with_buffer(9)struct ssh_notification_params(9)ssam_ssh_event_disable(9)ssam_get_firmware_version(9)ssam_ctrl_notif_display_off(9)ssam_ctrl_notif_display_on(9)ssam_ctrl_notif_d0_exit(9)ssam_ctrl_notif_d0_entry(9)ssam_nf_refcount_enable(9)ssam_nf_refcount_disable_free(9)ssam_notifier_register(9)__ssam_notifier_unregister(9)ssam_controller_event_enable(9)ssam_controller_event_disable(9)ssam_notifier_disable_registered(9)ssam_notifier_restore_registered(9)ssam_notifier_is_empty(9)ssam_notifier_unregister_all(9)ssam_irq_setup(9)ssam_irq_free(9)ssam_irq_arm_for_wakeup(9)ssam_irq_disarm_wakeup(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms