do_xfer(9)

📦 version 7.3.1, in nixpkgs unstable

💫 do_xfer(9) — like, the whole kernel API manual, but make it make sense 💫

okay so bestie, gather round, because we're reading a kernel API man page together and honestly? it's kind of a bop. this one is do_xfer, from the Kernel API Manual, and it's giving "one function, one job, zero drama" energy. let's get into it 🫶

✨ NAME ✨

do_xfer — Do one transfer. that's it. that's the whole vibe. one (1) transfer, done. periodt 💅

🌸 SYNOPSIS 🌸

here's the signature, copy it exactly bestie, no typos or the compiler will simply end you:

int do_xfer (const struct scmi_protocol_handle *ph , struct scmi_xfer
*xfer );

it returns an int, it takes those two pointers, and it is literally the main character of this page 👑

🎀 ARGUMENTS 🎀

two args, both pointers, both important, no cap:

  • ph — Pointer to SCMI protocol handle. yeah, that's the context-y one, your "who am I and what protocol am I speaking" situation 🦋
  • xfer — Transfer to initiate and wait for response. so you hand it over and then you wait, like a bestie waiting for a text back 😭

⭐ RETURN ⭐

okay so what comes back:

  • -ETIMEDOUT in case of no response — like, nobody picked up the phone 💀
  • if it's a transmit error, it returns the corresponding error — whatever went wrong on the way out, that's what you get
  • else, if all goes well — 0. a clean zero. the slay-est return value of all 🌈

👑 SEE ALSO 👑

this list is long and honestly it ate. every single one, in order, no skips, iykyk:

🧚 friendly reminder: everything literal up there — the function names, the (9) suffixes, the file path — is exact. don't go "fixing" the underscores or the double-underscore on __scmi_xfer_put, she's sensitive 🙈

💖 sign-off 💖

and that's the page! it lives under ./drivers/firmware/arm_scmi, dated October 2026, and it goes by do_xfer(9). mwah, go read driver.c, drink some water, and remember: wait for your response, bestie 💜✨

📦 where this page comes from