scmi_xfer_r...age_response(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… scmi_xfer_raw_wait_for_message_response β€” Kernel API Manual πŸŽ€

okay so bestie, welcome to the scmi_xfer_r...age_response(9) page ✨ (yes the title got abbreviated by the manpage machinery, we don't question it, we accept her πŸ’€). This is a Kernel API Manual moment and honestly? it's giving "small helper, huge responsibility" energy. Let's get into it 🫢


🌸 NAME 🌸

scmi_xfer_raw_wait_for_message_response β€” an helper to wait for a message reply to an xfer raw request on a specific channel for the required timeout πŸ’–

Like literally that's her whole job. She waits. On a specific channel. For the required timeout. Iconic behavior, no notes πŸ‘‘


✨ SYNOPSIS ✨

int scmi_xfer_raw_wait_for_message_response (struct scmi_chan_info
*cinfo , struct scmi_xfer *xfer , unsigned int timeout_ms );

three args, one int coming back at you, that's the whole vibe check πŸ¦‹


πŸ’œ ARGUMENTS πŸ’œ

  • cinfo β€” SCMI channel info πŸ’« this is the channel bestie, the one she's specifically waiting on, keep your eyes on her
  • xfer β€” Reference to the transfer being waited for 🌈 like, the actual thing you're sitting around hoping replies to you
  • timeout_ms β€” The maximum timeout in milliseconds ⏰ and yeah β€” maximum. she will not wait forever, she has boundaries

πŸŽ€ RETURN πŸŽ€

0 on Success, error otherwise πŸ™ˆ

that's it. that's the whole return section. zero means slay, anything else means something went sideways and you should go look at it fr fr


πŸ¦‹ SEE ALSO πŸ¦‹

so many friends, she's very well connected πŸ’… (iykyk):


ngl that's a whole ecosystem of functions right there β€” read a couple, they all hang out in the same driver file, it's giving one big friend group πŸ’€

and that's the page bestie!! πŸ“ she's sourced from ./drivers/firmware/arm_scmi and dated October 2026, so mark your calendar and stan responsibly πŸ’–βœ¨πŸŽ€πŸ«Ά

πŸ“¦ where this page comes from