scmi_raw_error_report(9)

📦 version 7.3.1, in nixpkgs unstable

💅 scmi_raw_error_report (9) — the Kernel API Manual, bestie edition

okay so you found yourself in the scmi_raw_error_report man page and honestly? good for you. this is the kernel API manual, SCMI corner, and this lil function is the one that catches the mess 🫶

✨ NAME ✨

scmi_raw_error_report — a helper that reports back the replies that timed out or were just generally unexpected. it's giving "you good? no? okay noted" 💀

🌸 SYNOPSIS 🌸

void scmi_raw_error_report (void *r , struct scmi_chan_info *cinfo , u32
msg_hdr , void *priv );

🎀 ARGUMENTS 🎀

  • r — an opaque reference to the raw instance configuration. opaque means don't peek, just pass it along bestie 🙈
  • cinfo — a reference to the channel to use to retrieve the broken xfer. it's the one who's gonna go get the messy transfer
  • msg_hdr — the SCMI message header of the message to fetch and report
  • priv — any private data related to the xfer

🦋 DESCRIPTION 🦋

okay so if Raw mode is enabled, this gets called from the SCMI core on the RX path whenever errors happen — its whole job is to save and enqueue the bad message payload carried by the message that has just been received. like catching the bad vibes mid-air and putting them in a jar 🫙✨

and here's the note, and it's important: we have to manually fetch any available payload into a temporary xfer to be able to save and enqueue the message. why? because the regular RX error path that had called this would not have fetched the message payload — it already classified the thing as an error. so no payload, no drama, just us doing it by hand 💅

🔥 SEE ALSO 🔥

that's a whole friend group right there, go say hi 👑

and that's the page!! this one lives in ./drivers/firmware/arm_scmi, dated October 2026 — go off, kernel era 🌈💜

📦 where this page comes from