ssam_control...event_enable(9)
okay so bestie, this page is from the Kernel API Manual, and it's all about ssam_controller_event_enable β yes, the event-enabling girly π
let's get into it.
π NAME π
ssam_controller_event_enable β enable the specified event. periodt β¨
πΈ SYNOPSIS πΈ
int ssam_controller_event_enable (struct ssam_controller *ctrl , struct
ssam_event_registry reg , struct ssam_event_id id , u8 flags );
π ARGUMENTS π
ctrlβ the controller you're enabling the event for, bestie.regβ the event registry to use for enabling the event.idβ the event ID that specifies which event gets enabled.flagsβ the SAM event flags used for enabling the event.
π¦ DESCRIPTION π¦
This call increments the event reference count of the specified event. If the event has not been enabled previously, it will be enabled by this call. like, it's doing the thing β¨
β NOTE β
In general, ssam_notifier_register with a non-observer notifier should be preferred for enabling/disabling events, as this will guarantee proper ordering and event forwarding in case of errors during event enabling/disabling. no cap, that's the preferred vibe π«Ά
π₯ RETURN π₯
Returns zero on success. It can also return:
-ENOSPCif the reference count for the specified event has reached its maximum.-ENOMEMif the corresponding event entry could not be allocated.
If this is the first time that this event has been enabled β i.e. the reference count was incremented from zero to one by this call β it returns the status of the event-enable EC-command. ikyk π
π SEE ALSO π
- Kernel file
./drivers/platform/surface/aggregator/controller.cβ the actual source, go off π 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_enable(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_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)
mwah π this page is from ./drivers/platform/surface/agg..., dated October 2026, and it's the ssam_control...event_enable(9) manual page. byeee bestie π«Άβ¨
π¦ 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