STRUCT STRATIX10_SVC_CB_DATA(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

struct stratix10_svc_cb_data β€” the callback data struct that comes flying back at you from the service layer ✨ (yes this is a (9) Kernel API Manual page, we're doing kernel internals today bestie, buckle up πŸ¦‹)


πŸ’– SYNOPSIS πŸ’–

okay so here's the whole vibe of the struct, literally exactly as it's written:

struct stratix10_svc_cb_data {
    u32 status;
    void *kaddr1;
    void *kaddr2;
    void *kaddr3;
 };

four little members, all main character energy, no cap πŸ’…


🌸 Members 🌸

  • status β€” the status of the command you sent out. like, did it slay or did it flop, this field is the vibe check 🫢
  • kaddr1 β€” the address of the 1st completed data block, or a command-specific payload, whichever fits the moment. for COMMAND_RSU_GET_DEVICE_INFO on SVC_STATUS_OK or SVC_STATUS_ERROR, this baby points to a struct arm_smccc_1_2_regs that got filled by the SMC/HVC return registers β€” so a0 is status, and a1–a4 are the packed device words per INTEL_SIP_SMC_RSU_GET_DEVICE_INFO πŸ‘‘ and on SVC_STATUS_NO_SUPPORT (that's the older firmware that does not handle this command, sad), kaddr1 is NULL. periodt.
  • kaddr2 β€” the address of the 2nd completed data block 😌
  • kaddr3 β€” the address of the 3rd completed data block ⭐

πŸ¦‹ SEE ALSO πŸ¦‹

basically the whole friend group, all hanging out in the Kernel file ./include/linux/firmware/intel/stratix10-svc-client.h:


πŸ’€ reminder bestie: this page lives at ./include/linux/firmware/intel, dated October 2026, and yes the man page title got truncated to struct strat..._svc_cb_data(9) which is honestly iconic of it πŸ™ˆπŸ’–

later bestie, go read your callbacks πŸ’œπŸ§šβœ¨

πŸ“¦ where this page comes from