ssam_contro...load_from_of(9)
π ssam_contro...load_from_of π
okay bestie so this is a page from the Kernel API Manual β yes, the kernel has lore too β and it's all about ssam_controller_caps_load_from_of. the shortened name up top is literally just ssam_contro...load_from_of(9) because manpage headers ran out of room, not because anyone's being shady β¨
π NAME π
ssam_controller_caps_load_from_of β loads controller capabilities from OF/DT. that's it, that's the whole job. she's a loader, she loads. periodt π
β¨ SYNOPSIS β¨
int ssam_controller_caps_load_from_of (struct device *dev , struct ssam_controller_caps *caps );
like look at her. returns an int, takes two args, zero drama. iconic.
π«Ά ARGUMENTS π«Ά
devβ a pointer to the controller device. lowkey the main character here β she's the device you're pulling info from πcapsβ where to store the capabilities in. it's the basket, bestie. the caps go IN thecaps. iykyk πΈ
π₯ RETURN π₯
returns zero on success β slay, ate, no notes β and a negative error code on failure π so like fr fr check that return value, do not just vibe past it.
π SEE ALSO π
ngl this list is giving "she has a whole extended friend group" β but every single one of them is real and you're gonna respect them π
Kernel file ./drivers/platform/surface/aggregator/controller.cβ the actual source file, the mothership πΈ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)β her ACPI-flavored sibling, the way that family stays consistent π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)β yes with the double underscore, don't come for her π«Ά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)
ok real talk bestie: everything above is the actual documented content, i didn't invent a single syscall. go read the kernel file if you wanna see her in her natural habitat π
and that's the whole vibe check π this page came out of ./drivers/platform/surface/agg... (the abbreviated path, she's shy), with a date of October 2026, and the footer's repeating the title ssam_contro...load_from_of(9) one more time for the cheap seats. mwah π go forth and load those caps π¦π
π¦ 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