rsu_send_msg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

rsu_send_msg β€” bestie, this is the one that sends a message to the Intel service layer ✨


✨ SYNOPSIS ✨

int rsu_send_msg (struct stratix10_rsu_priv *priv , enum
stratix10_svc_command_code command , unsigned long arg , rsu_callback
callback );

πŸŽ€ ARGUMENTS πŸŽ€

  • priv β€” pointer to rsu private data 🫢 lowkey just the private data for this rsu, hand it over and we're so good
  • command β€” the RSU status or update command πŸ‘‘ you're picking the vibe of the whole operation here
  • arg β€” the request argument, the bitstream address or notify status 🌈 so it's either the bitstream address or a notify status, depending on what you're doing, iykyk
  • callback β€” function pointer for the callback (status or update) πŸ¦‹ status callback or update callback, either way it's the thing that gets called back

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so here's the whole plot: this kicks off an Intel service layer transaction so the SMC call can happen β€” and that SMC call is literally required to get the RSU boot log or to set the address of the bitstream to boot after reboot 🧚✨

Heads up bestie: this call will block until the RSU lock can be acquired πŸ’€ like, it's not gonna just quietly give up, it waits its turn. No cap.

It returns 0 on success, or a negative errno on failure 😭 so check that return value, fr fr.


🌸 SEE ALSO 🌸

Kernel file ./drivers/firmware/stratix10-rsu.c πŸ“


And that's the whole thing, bestie β€” brought to you by ./drivers/firmware, stamped October 2026, living its best life as part of the Kernel API Manual πŸ’œπŸŽ€ slay, go read the source, mwah πŸ’…

πŸ“¦ where this page comes from