scmi_xfer_raw_channel_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… scmi_xfer_raw_channel_get(9) πŸ’…

okay so welcome to the Kernel API Manual, bestie β€” this is the page for scmi_xfer_raw_channel_get, and it’s giving very specific-channel-reference energy. πŸ’–

🌸 NAME 🌸

scmi_xfer_raw_channel_get β€” helper to get a reference to the proper channel to use for a specific protocol_id Raw transaction. Periodt. ✨

✨ SYNOPSIS ✨

struct scmi_chan_info * scmi_xfer_raw_channel_get (const struct
       scmi_handle *handle , u8 protocol_id );

πŸŽ€ ARGUMENTS πŸŽ€

  • handle β€” pointer to the SCMI entity handle. 🫢
  • protocol_id β€” identifier of the protocol. πŸ’«

πŸ¦‹ DESCRIPTION πŸ¦‹

Note that in a regular SCMI stack, usually, a protocol has to be defined in the DT to have an associated channel and be usable. But in Raw mode any protocol in range is allowed, re-using the Base channel, so as to enable fuzzing on any protocol without the need of a fully compiled DT. No cap. πŸ”₯

πŸ’œ RETURN πŸ’œ

A reference to the channel to use, or an ERR_PTR. That’s the whole return vibe. 😭

πŸ‘‘ SEE ALSO πŸ‘‘


okay bye bestie β€” this page comes from ./drivers/firmware/arm_scmi and is dated October 2026, from the Kernel API Manual obviously. Mwah πŸ’‹πŸ«Άβœ¨

πŸ“¦ where this page comes from