rpmsg: rpmsg_send() operations takes rpmsg_endpoint

The rpmsg_send() operations has been taking a rpmsg_device, but this
forces users of secondary rpmsg_endpoints to use the rpmsg_sendto()
interface - by extracting source and destination from the given data
structures. If we instead pass the rpmsg_endpoint to these functions a
service can use rpmsg_sendto() to respond to messages, even on secondary
endpoints.

In addition this would allow us to support operations on multiple
channels in future backends that does not support off-channel
operations.

Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

1 files changed, 2 insertions, 2 deletions

diff --git a/samples/rpmsg/rpmsg_client_sample.c b/samples/rpmsg/rpmsg_client_sample.c
index 7e17d1c0aaf2..37975eddd64e 100644
--- a/samples/rpmsg/rpmsg_client_sample.c
+++ b/samples/rpmsg/rpmsg_client_sample.c
@@ -47,7 +47,7 @@ static void rpmsg_sample_cb(struct rpmsg_channel *rpdev, void *data, int len,
         }
 
         /* send a new message now */
-        ret = rpmsg_send(rpdev, MSG, strlen(MSG));
+        ret = rpmsg_send(rpdev->ept, MSG, strlen(MSG));
         if (ret)
                 dev_err(&rpdev->dev, "rpmsg_send failed: %d\n", ret);
 }
@@ -67,7 +67,7 @@ static int rpmsg_sample_probe(struct rpmsg_channel *rpdev)
         dev_set_drvdata(&rpdev->dev, idata);
 
         /* send a message to our remote processor */
-        ret = rpmsg_send(rpdev, MSG, strlen(MSG));
+        ret = rpmsg_send(rpdev->ept, MSG, strlen(MSG));
         if (ret) {
                 dev_err(&rpdev->dev, "rpmsg_send failed: %d\n", ret);
                 return ret;