rpmsg_send(9)

📦 version 7.3.1, in nixpkgs unstable

💌 rpmsg_send(9) — the Kernel API Manual, bestie edition

okay so you found the rpmsg_send(9) page, and honestly? good for you. this is the one that actually pushes your bytes across the void to the remote processor. let's get into it ✨

🌸 NAME

rpmsg_send — send a message across to the remote processor 🫶

🎀 SYNOPSIS

int rpmsg_send (struct rpmsg_endpoint *ept , const void *data , int len
);

like, that's the whole vibe. three args, one int coming back at you. 💅

🦋 ARGUMENTS

  • ept — the rpmsg endpoint. your lil handle on the conversation, bestie 🎀
  • data — payload of message. the actual stuff you're shipping 📦
  • len — length of payload. how many bytes are you sending, no cap 🔢

✨ DESCRIPTION

so here's the tea: this function sends data of length len on the ept endpoint. that's it, that's the job. 🌈

the message gets sent to the remote processor that the ept endpoint belongs to — and it uses ept's address plus its associated rpmsg device destination addresses to figure out where it's going. iykyk. 💫

now for the part you actually need to know 👀 — in case there are no TX buffers available, the function will block until one becomes available, or a timeout of 15 seconds elapses. so yeah, it'll just sit there waiting and you'll be like "hello??" 😭 and when that timeout hits, -ERESTARTSYS is returned. note it. memorize it. 🫡

⚠️ important vibe check: this can only be called from process context (for now). like, that's the rule. 💀

👑 RETURN

0 on success, and an appropriate error value on failure. that's it. slay. ✅

🔥 SEE ALSO

Kernel file ./drivers/rpmsg/rpmsg_core.c — go read it, it's giving main character energy 📖

and that's the whole page, bestie 💖 it lives in ./drivers/rpmsg, dated October 2026, and it's literally the rpmsg_send(9) manual — go send some messages, you've got this 🧚‍♀️⭐

📦 where this page comes from