STRUCT CROS_EC_XFER_WORK_PARAMS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

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

okay so this is a page from the Kernel API Manual, and honestly? it's giving "small but mighty" ✨ β€” we're talking about the params struct for our high priority workers, no cap. let's get into it 🫢


🌸 NAME 🌸

struct cros_ec_xfer_work_params β€” literally the params for our high priority workers πŸ’…


✨ SYNOPSIS ✨

struct cros_ec_xfer_work_params {
    struct kthread_work work;
    cros_ec_xfer_fn_t fn;
    struct cros_ec_device *ec_dev;
    struct cros_ec_command *ec_msg;
    int ret;
 };

like, that's the whole vibe right there πŸŽ€ copy it exactly bestie, don't be creative with it


πŸ¦‹ Members πŸ¦‹

so every field is a little main character in its own right, let's meet them πŸ‘‘

  • work β€” the work_struct you need to queue work. that's it, that's her job, and she does it slayfully πŸ’…
  • fn β€” the function to use to transfer. yes, the function πŸ”₯
  • ec_dev β€” the ChromeOS EC device 🌈 the whole reason we're here
  • ec_msg β€” the message to transfer πŸ“¨ she's carrying the message, literally
  • ret β€” the return value of the function. the receipts, the verdict, the final word πŸ’€

⭐ SEE ALSO ⭐

iykyk, go read the Kernel file ./drivers/platform/chrome/cros_ec_spi.c and also these iconic siblings:


bestie heads up 🫢 this page lives under ./drivers/platform/chrome β€” that's the neighborhood, that's the address, memorize it 🧚

and that's the whole page, no notes πŸ’œ huge thanks to the ./drivers/platform/chrome crew, this one's dated October 2026, and yes the manual name is struct cros..._work_params(9) β€” she's long, she's mysterious, we love her 😭🌸 periodt ✨

πŸ“¦ where this page comes from