cros_ec_cmd_xfer_rpmsg(9)

💅 cros_ec_cmd_xfer_rpmsg(9) — from the Kernel API Manual, bestie 🎀

Okay so real talk, this page is short and honestly a little bit of a jumpscare, but we're gonna get through it together. Strap in ✨

---

🌸 NAME 🌸

cros_ec_cmd_xfer_rpmsg — the function that's supposed to transfer a message over rpmsg and receive the reply 💌 (emphasis on "supposed to", keep reading, iykyk)

---

🦋 SYNOPSIS 🦋

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

So it returns an int, it takes two pointers, and that's the whole vibe check 💀

---

💖 ARGUMENTS 💖

• ec_dev — the ChromeOS EC device 🎮 like, the EC in question, the main character of this story
• ec_msg — the message you're trying to transfer 📨 the one that's not going anywhere, bestie

---

🙈 DESCRIPTION 🙈

Okay so here's the tea ☕ and it's not great tea:

This one is only used for old EC proto version, and it is not supported for this driver.

Not me showing up to a function that literally says "not supported" 😭 it's giving decorative. It's giving "we keep you around for legacy reasons only." Lowkey iconic of it to just exist and do nothing, honestly. Periodt.

---

💀 RETURN 💀

-EINVAL

That's it. That's the whole return section. One value. Negative. A little bit of a read, ngl 🌸

---

🔥 SEE ALSO 🔥

If you're nosy (respectfully 🫶) here's where to go next:

• Kernel file ./drivers/platform/chrome/cros_ec_rpmsg.c
• struct cros_ec_rpmsg_response(9)
• struct cros_ec_rpmsg(9)
• cros_ec_pkt_xfer_rpmsg(9) — the sibling that actually does stuff 👑

---

⭐ Quick reminder bestie: it's only for old EC proto version and it's not supported for this driver. Don't build your whole plan around it, mmkay? 💜

---

Alright that's the page! This little gem lives over in ./drivers/platform/chrome, and it's dated October 2026 🍓 — signed, sealed, delivered, and formatted by your fave kernel-fluent bestie 💅✨