scmi_xfer_get(9)

📦 version 7.3.1, in nixpkgs unstable

💅 scmi_xfer_get(9) — like, the Kernel API Manual, bestie ✨

Okay so real talk, this page lives in the Kernel API Manual and it's literally called scmi_xfer_get. Buckle up, we're allocating a message 🎀

🦋 NAME

scmi_xfer_get — Allocate one message. That's it, that's the whole vibe. One message, freshly allocated, no cap 💖

✨ SYNOPSIS

struct scmi_xfer * scmi_xfer_get (const struct scmi_handle *handle ,
struct scmi_xfers_info *minfo );

🌸 ARGUMENTS

  • handle — Pointer to the SCMI entity handle. Very demure, very "here's who I am" energy 🫶
  • minfo — Pointer to the Tx/Rx Message management info, and bestie, it's based on channel type. Channel type matters, don't forget it 💅

💜 DESCRIPTION

So this is a helper function — and when I say helper I mean it's the one doing all the work for everybody else 😭 Various message functions that are exposed to clients of this driver use it to allocate a message traffic event.

Here's the little routine it runs:

  • Picks an xfer from the free list free_xfers (if any are available, key detail, "if any available")
  • Performs a basic initialization on it ✨
Lowkey important note: at this point, still no sequence number is assigned to the allocated xfer, and it is not registered as a pending transaction. Like, it's not official yet, it's just chilling 🙈

The successfully initialized xfer is refcounted. Slay 💅

🔥 CONTEXT

It holds xfer_lock while manipulating free_xfers. That's the whole context section, she's short and iconic 👑

⭐ RETURN

An initialized xfer if all went fine 💖 Else, a pointer error 💀

🧚 SEE ALSO

Kernel file ./drivers/firmware/arm_scmi/driver.c — go read it, iykyk 🍓

Like I said. The whole group chat 🫶

That's the page, babes 💖 courtesy of <rainbow>./drivers/firmware/arm_scmi</rainbow> and it's dated October 2026 — see you then, mwah 💅🎀

📦 where this page comes from