wilco_ec_transfer(9)

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

okay so real talk, this is a page from the Kernel API Manual (wilco_ec_transfer, section 9) and it's literally the function that does the actual data transfer. no cap, that's the whole vibe. let's get into it 🎀

---

✨ NAME ✨

wilco_ec_transfer — perform actual data transfer. that's it, that's the job. she moves the data. slay 💅

---

🌸 SYNOPSIS 🌸

int wilco_ec_transfer (struct wilco_ec_device *ec , struct wilco_ec_message *msg , struct wilco_ec_request *rq );

it's giving "three pointers walk into a function" and honestly? iconic 🦋

---

💖 ARGUMENTS 💖

• ec — the EC device. the main character, lowkey. everything happens around her 👑
• msg — EC message data for request and response. yes bestie, both directions, she's versatile 💫
• rq — the filled-in request structure. already prepped and ready to go, we love a prepared queen 🎀

---

🔒 CONTEXT 🔒

bestie, listen. ec->mailbox_lock should be held while using this function. this is not a drill, this is not optional vibes, this is a lock. hold it. periodt 💀

---

⭐ RETURN ⭐

returns the number of bytes received, or a negative error code on failure. so like, if it's a positive number — we ate 🔥. if it's negative — something went wrong, and it's a whole mood 😭

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/platform/chrome/wilco_ec/mailbox.c — the source, go read her fr fr 📖
• wilco_ec_response_timed_out(9)
• wilco_ec_checksum(9)
• wilco_ec_prepare(9)
• wilco_ec_mailbox(9)

the whole friend group, honestly 🫶

---

and that's the page!! 🧚 this little number lives at ./drivers/platform/chrome/wilc... (they truncated it, rip 💀), dated October 2026, and it signs off as wilco_ec_transfer(9) — same energy as the header, because consistency is a love language 💜 byeee 🍓