scmi_xfer_inflight_register(9)

📦 version 7.3.1, in nixpkgs unstable

💅 scmi_xfer_inflight_register(9) — from the Kernel API Manual, bestie

okay so picture this: it's a kernel API manual page, the title is scmi_xfer_inflight_register(9), and it's about to become your new obsession. let's get into it ✨

🌸 NAME 🌸

scmi_xfer_inflight_register — literally just "try to register an xfer as in-flight", that's the whole vibe 🦋

✨ SYNOPSIS ✨

int scmi_xfer_inflight_register (struct scmi_xfer *xfer , struct
       scmi_xfers_info *minfo );

like, that's the signature, no notes 💅

🎀 ARGUMENTS 🎀

  • xfer — the xfer you're registering. that's it. that's the girl 🫶
  • minfo — a pointer to the Tx/Rx Message management info, and which one you get depends on the channel type. iykyk 🌈

💖 DESCRIPTION 💖

okay so real talk, this helper does NOT assume anything about the sequence number that was already baked into the xfer you handed it. nope, not a single assumption, she refuses 🙈

so what does it do instead? it checks first whether that sequence number can be mapped to a free slot — and if another xfer with the same sequence number is currently still registered as in-flight, it fails with an error. no cap, that's the whole check 💀

bestie please note: the "does NOT assume anything about the sequence number" part is the main character of this paragraph. don't skip her 👑

⭐ RETURN ⭐

  • 0 on Success 🎉
  • -EBUSY if the sequence number embedded in the xfer could not be mapped to a free slot in the xfer_alloc_table. like, the table said no 😭

🔥 SEE ALSO 🔥

so there's a lot here, and every single one of these is iconic in her own way:

and that's the page, bestie 💜 she lives in ./drivers/firmware/arm_scmi, she's dated October 2026, and her name is — say it with me — scmi_xfer_inflight_register(9). slay 🎀✨🦋

📦 where this page comes from