rsu_async_ge...ble_callback(9)
β¨ rsu_async_get_spt_table_callback β¨
okay so bestie, welcome to the Kernel API Manual π
this one's all about rsu_async_get_spt_table_callback β the callback you hand to rsu_async_send() so it can go grab the SPT table info for you. no cap, that's literally its whole vibe.
πΈ NAME πΈ
rsu_async_get_spt_table_callback β the callback to be used by the rsu_async_send() to retrieve the SPT table information. periodt. π
π¦ SYNOPSIS π¦
void rsu_async_get_spt_table_callback (struct device *dev , struct
stratix10_rsu_priv *priv , struct stratix10_svc_cb_data *data );
like, that's the whole signature, character for character, don't come for me π«Ά
π ARGUMENTS π
devβ pointer to device object. it's giving "who am I" energy β¨privβ pointer to priv object. your private little stash of info πdataβ pointer to callback data structure. the lil care package that shows up when the callback fires π
π SEE ALSO π
bestie, the lore is deep. go read these, fr fr:
- Kernel file
./drivers/firmware/stratix10-rsu.c rsu_device_info_set_from_packed(9)struct stratix10_rsu_priv(9)rsu_device_info_invalidate(9)rsu_status_callback(9)rsu_async_status_callback(9)rsu_command_callback(9)rsu_retry_callback(9)rsu_max_retry_callback(9)rsu_dcmf_version_callback(9)rsu_dcmf_status_callback(9)rsu_get_device_info_callback(9)__rsu_send_msg_locked(9)rsu_send_msg(9)rsu_try_send_msg(9)soc64_async_callback(9)rsu_send_async_msg(9)
and that's the whole page, bestie!! sourced from ./drivers/firmware, dated October 2026, and yeah β the page name is literally rsu_async_ge...ble_callback(9) because the header got truncated and we're just living with it ππ slay. π§ββοΈπβ¨
π¦ 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