rpmsg: rpmsg_send() operations takes rpmsg_endpoint
authorBjorn Andersson <bjorn.andersson@linaro.org>
Thu, 1 Sep 2016 22:27:55 +0000 (15:27 -0700)
committerBjorn Andersson <bjorn.andersson@linaro.org>
Fri, 9 Sep 2016 05:15:19 +0000 (22:15 -0700)
commit2a48d7322dc88f1bc6c8bd9e087fc6341ba659fd
tree5e7f22bdf638a51576523e631589d52cdadf3012
parent4dffed5b3ac796bcaf040ca1f64e650f9263363e
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>
drivers/rpmsg/virtio_rpmsg_bus.c
include/linux/rpmsg.h
samples/rpmsg/rpmsg_client_sample.c