do_cros_ec_cmd_xfer_spi(9)

💅 do_cros_ec_cmd_xfer_spi — the Kernel API Manual moment 🎀

okay so bestie, welcome to the Kernel API Manual entry for do_cros_ec_cmd_xfer_spi(9) — yes the (9) is part of the name, it's giving section-nine realness and we respect it 💖

---

✨ NAME ✨

do_cros_ec_cmd_xfer_spi — literally just transfer a message over SPI and receive the reply 🦋 that's it, that's the whole vibe

---

🌸 SYNOPSIS 🌸

int do_cros_ec_cmd_xfer_spi (struct cros_ec_device *ec_dev , struct cros_ec_command *ec_msg );

the way it takes two pointers and hands you back an int… main character energy fr fr 👑

---

🎀 ARGUMENTS 🎀

• ec_dev — the ChromeOS EC device 💅 like, the actual embedded controller you're talking to, no cap
• ec_msg — the message to transfer ✨ the whole reason we're here, the payload, the moment

---

🦋 SEE ALSO 🦋

sibling entries, all iconic, all linked, go read them:

• Kernel file ./drivers/platform/chrome/cros_ec_spi.c
• struct cros_ec_spi(9)
• struct cros_ec_xfer_work_params(9)
• receive_n_bytes(9)
• cros_ec_spi_receive_packet(9)
• cros_ec_spi_receive_response(9)
• do_cros_ec_pkt_xfer_spi(9)

---

bestie note: the whole page is short and sweet, but every name up there is exact — don't go renaming do_cros_ec_pkt_xfer_spi to something cuter, it will NOT slay, it will just break the build 😭

---

and that's the page 🫶 brought to you by ./drivers/platform/chrome, dated October 2026, filed under do_cros_ec_cmd_xfer_spi(9) — periodt 💜🌸