rsu_retry_callback(9)

Okay bestie, this is rsu_retry_callback(9) from the Kernel API Manual — and yes, it's giving firmware callback main character energy. 💅✨

🎀 NAME 🎀

rsu_retry_callback — callback from the Intel service layer for getting the current image's retry counter from the firmware. Periodt. 🫶

✨ SYNOPSIS ✨

void rsu_retry_callback (struct stratix10_svc_client *client , struct stratix10_svc_cb_data *data );

🌸 ARGUMENTS 🌸

• client — pointer to client. Lowkey just your client pointer, bestie. 🎀
• data — pointer to callback data structure. That's the callback data structure tea. 💖

🦋 DESCRIPTION 🦋

Okay so this is a callback from the Intel service layer for the retry counter. The retry counter is used by user to know how many times the images is still allowed to reload itself before giving up and starting RSU fail-over flow. That's the whole plot — no cap. 💅🔥

🔥 SEE ALSO 🔥

Kernel file ./drivers/firmware/stratix10-rsu.c — go read it, iykyk. 👑

• 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_max_retry_callback(9)
• rsu_dcmf_version_callback(9)
• rsu_dcmf_status_callback(9)
• rsu_get_device_info_callback(9)
• rsu_async_get_spt_table_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)

Okay that's the whole vibe. Big shoutout to source ./drivers/firmware, date October 2026, and rsu_retry_callback(9) — catch you in the kernel, bestie! 💜🫶✨