user/sven/linux.git/include/linux/rpmsg.h, branch v4.9.10Linux Kernel
https://git.stealer.net/cgit.cgi/user/sven/linux.git/atom?h=v4.9.102016-09-09T05:15:25Zrpmsg: Allow callback to return errors2016-09-09T05:15:25ZBjorn Anderssonbjorn.andersson@linaro.org2016-09-01T22:28:08Zurn:sha1:4b83c52a21cf5a7421b7c28bebf8ff28ba96ceb9
Some rpmsg backends support holding on to and redelivering messages upon
failed handling of them, so provide a way for the callback to report and
error and allow the backends to handle this.
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
rpmsg: Move virtio specifics from public header2016-09-09T05:15:25ZBjorn Anderssonbjorn.andersson@linaro.org2016-09-01T22:28:07Zurn:sha1:e88dae5da46d3989fd6a83dd9f6806777b20d1ae
Move virtio rpmsg implementation details from the public header file to
the virtio rpmsg implementation.
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
rpmsg: virtio: Hide vrp pointer from the public API2016-09-09T05:15:24ZBjorn Anderssonbjorn.andersson@linaro.org2016-09-01T22:28:06Zurn:sha1:3bf950ff23337fc812736520ff9d098284187844
Create a container struct virtio_rpmsg_channel around the rpmsg_channel
to keep virtio backend information separate from the rpmsg and public
API. This makes the public structures independant of virtio.
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
rpmsg: Hide rpmsg indirection tables2016-09-09T05:15:24ZBjorn Anderssonbjorn.andersson@linaro.org2016-09-01T22:28:05Zurn:sha1:fade037e0fd504cd02f51d280928d89c75527f2e
Move the device and endpoint indirection tables to the rpmsg internal
header file, to hide them from the public API.
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
rpmsg: Move endpoint related interface to rpmsg core2016-09-09T05:15:22ZBjorn Anderssonbjorn.andersson@linaro.org2016-09-01T22:28:01Zurn:sha1:c9bd6f422090b874b5877b4cedcd7757eac33117
Move the rpmsg_send() and rpmsg_destroy_ept() interface to the rpmsg
core, so that we eventually can hide the rpmsg_endpoint ops from the
public API.
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
rpmsg: Indirection table for rpmsg_endpoint operations2016-09-09T05:15:21ZBjorn Anderssonbjorn.andersson@linaro.org2016-09-01T22:28:00Zurn:sha1:8a228ecfe086b84e237a8d78be079e286e1ea67b
Add indirection table for rpmsg_endpoint related operations and move
virtio implementation behind this, this finishes of the decoupling of
the virtio implementation from the public API.
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
rpmsg: Introduce indirection table for rpmsg_device operations2016-09-09T05:15:20ZBjorn Anderssonbjorn.andersson@linaro.org2016-09-01T22:27:58Zurn:sha1:36b72c7dca718717108120cdff7b56258a8862b4
To allow for multiple backend implementations add an indireection table
for rpmsg_device related operations and move the virtio implementation
behind this table.
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
rpmsg: Clean up rpmsg device vs channel naming2016-09-09T05:15:20ZBjorn Anderssonbjorn.andersson@linaro.org2016-09-01T22:27:57Zurn:sha1:92e1de51bf2cb8d49adc8925abe56ce84911a232
The rpmsg device representing struct is called rpmsg_channel and the
variable name used throughout is rpdev, with the communication happening
on endpoints it's clearer to just call this a "device" in a public API.
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
rpmsg: Make rpmsg_create_ept() take channel_info struct2016-09-09T05:15:19ZBjorn Anderssonbjorn.andersson@linaro.org2016-09-01T22:27:56Zurn:sha1:2b263d2408663a36c14a0aa1f765b2c84b92ea18
As we introduce support for additional rpmsg backends, some of these
only supports point-to-point "links" represented by a name. By making
rpmsg_create_ept() take a channel_info struct we allow for these
backends to either be passed a source address, a destination address or
a name identifier.
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
rpmsg: rpmsg_send() operations takes rpmsg_endpoint2016-09-09T05:15:19ZBjorn Anderssonbjorn.andersson@linaro.org2016-09-01T22:27:55Zurn:sha1:2a48d7322dc88f1bc6c8bd9e087fc6341ba659fd
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>