rpmsg_sendto(9)

📦 version 7.3.1, in nixpkgs unstable

💖 rpmsg_sendto(9) 💖

okay so bestie, this is the Kernel API Manual page for rpmsg_sendto(9), and it's giving “send a message to a remote processor but make it destination-specific.” 🫶✨

✨ NAME ✨

rpmsg_sendto — send a message across to the remote processor, specify dst

🎀 SYNOPSIS 🎀

int rpmsg_sendto (struct rpmsg_endpoint *ept , const void *data , int
       len , u32 dst );

💅 ARGUMENTS 💅

  • ept — the rpmsg endpoint. the main character you're sending through. 👑
  • data — payload of message. the actual message snack. 🍓
  • len — length of payload. how much of the payload you're bringing. ✨
  • dst — destination address. where it's headed, no cap. 🎯

🌸 DESCRIPTION 🌸

okay so this function sends data of length len to the remote dst address. periodt. The message will be sent to the remote processor which the ept endpoint belongs to, using ept's address as source. iykyk. ✨

In case there are no TX buffers available, the function will block until one becomes available, or a timeout of 15 seconds elapses. 😭 When the latter happens, -ERESTARTSYS is returned. not me waiting on a buffer like it's a text back. 💀

bestie, it can only be called from process context (for now). that's the vibe check. 💅

🦋 RETURN 🦋

0 on success and an appropriate error value on failure. slay when it's 0, obviously. 💖

🔥 SEE ALSO 🔥

Kernel file: ./drivers/rpmsg/rpmsg_core.c

mwah 💋 this page's source/version line lives at ./drivers/rpmsg, the date is October 2026, and the page is literally rpmsg_sendto(9) — bye bestie! 🫶✨

📦 where this page comes from