STRUCT SCMI_XFER_RAW_WAITER(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct scmi_xfer_raw_waiter(9) πŸ’–

okay bestie, we’re in the Kernel API Manual and this page is literally all about struct scmi_xfer_raw_waiter β€” the structure that describes an xfer you’re waiting for. no cap, that’s the whole assignment. πŸŽ€


✨ NAME ✨

struct scmi_xfer_raw_waiter β€” structure to describe an xfer to be waited for. periodt. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

okay so the struct itself is giving exactly this, verbatim:

struct scmi_xfer_raw_waiter {
    unsigned long start_jiffies;
    struct scmi_chan_info *cinfo;
    struct scmi_xfer *xfer;
    struct completion async_response;
    struct list_head node;
 };

🌸 Members 🌸

every member is iconic in its own way, so let’s go through them one by one, fr fr:

  • start_jiffies β€” the timestamp in jiffies of when this structure was queued. ⏱️
  • cinfo β€” a reference to the channel to use for this transaction. it’s giving β€œthis is the lane we’re using” energy. πŸ›£οΈ
  • xfer β€” a reference to the xfer to be waited for. main character xfer, honestly. πŸ‘‘
  • async_response β€” a completion to be, optionally, used for async waits: it will be setup by scmi_do_xfer_raw_start, if needed, to be pointed at by xfer->async_done. yes bestie, that exact chain. πŸ”—
  • node β€” a list node. simple, cute, does its job. πŸŽ€

πŸ’œ SEE ALSO πŸ’œ

go off and read these, bestie β€” they’re all linked from this page:


mwah πŸ’‹ this lil’ page comes from ./drivers/firmware/arm_scmi, October 2026, and it is the struct scmi_xfer_raw_waiter(9) manual β€” iconic, printed, done. πŸ’–

πŸ“¦ where this page comes from