scmi_raw_message_report(9)

📦 version 7.3.1, in nixpkgs unstable

💅 scmi_raw_message_report — a Kernel API Manual moment (yes, that's the manual, we're in it)

okay so bestie, welcome to scmi_raw_message_report(9) — the little helper whose whole entire job is reporting valid responses and notifications back to raw message requests. it's giving backstage pass energy fr fr 🎀

✨ NAME ✨

scmi_raw_message_report — the helper that reports valid responses/notifications back to raw message requests. that's it, that's the gig 🫶

🌸 SYNOPSIS 🌸

void scmi_raw_message_report (void *r , struct scmi_xfer *xfer ,
       unsigned int idx , unsigned int chan_id );

🦋 ARGUMENTS 🦋

  • r — an opaque reference to the raw instance configuration. opaque means don't peek, bestie, just pass it along 🙈
  • xfer — the xfer holding the message we're about to report. it's the star of the show ✨
  • idx — the index of the queue. which queue? that queue. the one at this index 💅
  • chan_id — the channel ID to use. gotta know which channel we're on, iykyk 📡

💖 DESCRIPTION 💖

okay so here's the vibe: if Raw mode is enabled, this function gets called from the SCMI core on the regular RX path, and its whole job is to save and enqueue the response/notification payload that this xfer is carrying into a dedicated scmi_raw_buffer for later consumption by the user. no cap, that's the whole plot 🌈

and the way this slaps is that the caller can free the related xfer immediately afterwards — like, immediately immediately — and then the user can read back the raw message payload at its own pace (if ever) without holding an xfer for too long. main character energy for the user, honestly, they get to take their sweet time 👑

🔥 SEE ALSO 🔥

lowkey a whole friend group of SEE ALSOs and they all ate 💀 go read them, bestie, they're literally the lore

and that's the page!! mwah 💋 this came from ./drivers/firmware/arm_scmi, dated October 2026 — so like, remember us when you're famous, k? bye bestie, slay your xfers 🧚💜

📦 where this page comes from