linux-toradex.git/drivers/rpmsg/qcom_glink_smem.c, branch v4.18

rpmsg: glink: Switch to SPDX license identifier

2018-06-04T00:37:15+00:00

Use the appropriate SPDX license identifier in various rpmsg
glink driver source files and drop the previous boilerplate
license text.

Signed-off-by: Suman Anna 
Signed-off-by: Bjorn Andersson

rpmsg: glink: use put_device() if device_register fail

2018-03-18T04:45:57+00:00

if device_register() returned an error! Always use put_device()
to give up the reference initialized. And unregister device for
other return error.

Signed-off-by: Arvind Yadav 
Signed-off-by: Bjorn Andersson

rpmsg: glink: smem: Ensure ordering during tx

2017-12-19T05:47:43+00:00

Ensure the ordering of the fifo write and the update of the write index,
so that the index is not updated before the data has landed in the fifo.

Acked-By: Chris Lew 
Reported-by: Arun Kumar Neelakantam 
Signed-off-by: Bjorn Andersson

drivers: rpmsg: remove duplicate includes

2017-12-06T21:59:14+00:00

These duplicate includes have been found with scripts/checkincludes.pl but
they have been removed manually to avoid removing false positives.

Signed-off-by: Pravin Shedge 
Signed-off-by: Bjorn Andersson

rpmsg: glink: Make RX FIFO peak accessor to take an offset

2017-08-30T03:34:13+00:00

To fully read the received rx data from FIFO both the command and data
has to be read. Currently we read command, data separately and process
them. By adding an offset parameter to RX FIFO peak accessor, command
and data can be read together, simplifying things.  So introduce this.

Acked-by: Arun Kumar Neelakantam 
Signed-off-by: Sricharan R 
Signed-off-by: Bjorn Andersson

rpmsg: glink: Add support for TX intents

2017-08-30T03:34:13+00:00

Intents are nothing but pre-allocated buffers of appropriate size that
are allocated on the local side and communicated to the remote side and
the remote stores the list of intent ids that it is informed.

Later when remote side is intenting to send data, it picks up a right
intent (based on the size) and sends the data buffer and the intent id.
Local side receives the data and copies it to the local intent buffer.

The whole idea is to avoid stalls on the transport for allocating
memory, used for copy based transports.

When the remote request to allocate buffers using CMD_RX_INTENT_REQ, we
allocate buffers of requested size, store the buffer id locally and also
communicate the intent id to the remote.

Acked-by: Arun Kumar Neelakantam 
Signed-off-by: Sricharan R 
Signed-off-by: Bjorn Andersson

rpmsg: glink: Add support for transport version negotiation

2017-08-30T03:34:12+00:00

G-link supports a version number and feature flags for each transport.
A combination of the version number and feature flags enable/disable:

 (*) G-Link software updates for each edge
 (*) Individual features for each edge

Endpoints negotiate both the version and the supported flags when
the transport is opened and they cannot be changed after negotiation has
been completed.

Each full implementation of G-Link must support a minimum of the current
version, the previous version, and the base negotiation version called v0.

Acked-by: Arun Kumar Neelakantam 
Signed-off-by: Sricharan R 
Signed-off-by: Bjorn Andersson

rpmsg: glink: Introduce glink smem based transport

2017-08-30T03:33:57+00:00

The glink protocol supports different types of transports (shared
memory). With the core protocol remaining the same, the way the
transport's memory is probed and accessed is different. So add support
for glink's smem based transports.

Adding a new smem transport register function and the fifo accessors for
the same.

Acked-by: Arun Kumar Neelakantam 
Signed-off-by: Sricharan R 
Signed-off-by: Bjorn Andersson