27 Oct, 2020

1 commit


30 Sep, 2020

1 commit

  • RPMSG unifies various transports that provide IPC to a remote proc.
    Some of these transports require some set of side band signalling in
    order to meet the specifications of the protocol they implement.

    The GLINK native transport supports the tty serial signals to start
    communication with modems that expect to receive the DTR serial signal.

    Extend the rpmsg core with an interface to send and receive sideband
    signals for the transports that need it.

    Bug: 161128971
    Link: https://lore.kernel.org/lkml/1593182819-30747-2-git-send-email-deesin@codeaurora.org/
    Change-Id: I54539d8ddce1bfaec9016c2bec9b5a1372601995
    Signed-off-by: Chris Lew
    (cherry picked from commit 6839fc80fe1f6564eb6a0fc0fd081d459ec6c61b)

    Chris Lew
     

15 Sep, 2020

1 commit

  • In RPMSG GLINK the chrdev device will allocate an ept as part of the
    rpdev creation. This device will not register endpoint ops even though
    it has an allocated ept. Protect against the case where the device is
    being destroyed.

    Signed-off-by: Chris Lew
    Signed-off-by: Arun Kumar Neelakantam
    Signed-off-by: Deepak Kumar Singh
    Link: https://lore.kernel.org/r/1593017121-7953-3-git-send-email-deesin@codeaurora.org
    Signed-off-by: Bjorn Andersson

    Chris Lew
     

17 Apr, 2020

1 commit


27 Aug, 2019

1 commit


22 May, 2019

1 commit


31 Jul, 2018

1 commit

  • Some of the rpmsg devices need to switch on power domains to communicate
    with remote processor. For example on Qualcomm DB820c platform LPASS
    power domain needs to switched on for any kind of audio services.
    This patch adds the missing power domain support in rpmsg core.

    Without this patch attempting to play audio via QDSP on DB820c would
    reboot the system.

    Signed-off-by: Srinivas Kandagatla
    Signed-off-by: Bjorn Andersson

    Srinivas Kandagatla
     

04 Jun, 2018

1 commit


26 Apr, 2018

1 commit

  • This patch adds "driver_override" device attribute for rpmsg_device which
    will allow users to explicitly specify the rpmsg_driver to be used via
    sysfs entry.

    The "driver_override" device attribute implemented here is very similar
    to "driver_override" implemented for platform, pci, and amba bus types.

    One important use-case of "driver_override" device attribute is to force
    use of rpmsg_chrdev driver for certain rpmsg_device instances.

    Signed-off-by: Anup Patel
    Signed-off-by: Bjorn Andersson

    Anup Patel
     

28 Mar, 2018

1 commit


29 Nov, 2017

1 commit


07 Jul, 2017

1 commit

  • Pull rpmsg updates from Bjorn Andersson:
    "This introduces the Qualcomm GLINK protocol driver and
    DeviceTree-based modalias support, as well as a number of smaller
    fixes"

    * tag 'rpmsg-v4.13' of git://github.com/andersson/remoteproc:
    rpmsg: Make modalias work for DeviceTree based devices
    rpmsg: Drop VIRTUALIZATION dependency from RPMSG_VIRTIO
    rpmsg: Don't overwrite release op of rpdev
    rpmsg: virtio_rpmsg_bus: cleanup multiple assignment to ops
    rpmsg: virtio_rpmsg_bus: fix nameservice address
    rpmsg: cleanup incorrect function in dev_err message
    rpmsg: virtio_rpmsg_bus: fix announce for devices without endpoint
    rpmsg: Introduce Qualcomm RPM glink driver
    soc: qcom: Add device tree binding for GLINK RPM
    rpmsg: Release rpmsg devices in backends

    Linus Torvalds
     

29 Jun, 2017

1 commit


27 Jun, 2017

1 commit

  • b0b03b811963 ("rpmsg: Release rpmsg devices in backends") attempted to
    correct the ownership of freeing rpmsg device memory. But the patch
    is not complete, in that the rpmsg core will overwrite the release op as
    the device is being registered.

    Fixes: b0b03b811963 ("rpmsg: Release rpmsg devices in backends")
    Reported-by: Henri Roosen
    Signed-off-by: Bjorn Andersson

    Bjorn Andersson
     

09 Jun, 2017

1 commit


13 Feb, 2017

1 commit

  • The parameter validation incorrectly returned an ERR_PTR(), which is not
    handled by the callers to rpmsg_create_ept(), per the definition NULL
    should be returned.

    Fixes: 93e9324431c9 ("rpmsg: Handle invalid parameters in public API")
    Reported-by: Dan Carpenter
    Signed-off-by: Bjorn Andersson

    Bjorn Andersson
     

19 Jan, 2017

1 commit


30 Dec, 2016

1 commit

  • Since commit 4dffed5b3ac796b ("rpmsg: Name rpmsg devices based on
    channel id"), it is no more possible for a firmware to register twice
    a service (on different endpoints). rpmsg_register_device function
    is failing when calling device_add for the second time as second
    device has the same name as first one already register.
    It is because name is based only on service name and so is not more
    unique. Previously name was unique thanks to the use of rpmsg_dev_index.

    This patch adds destination and source endpoint numbers device name to
    create an unique identifier.

    Fixes: 4dffed5b3ac7 ("rpmsg: Name rpmsg devices based on channel id")
    Acked-by: Peter Griffin
    Signed-off-by: Loic Pallardy
    [bjorn: flipped name and address in device name]
    Signed-off-by: Bjorn Andersson

    Loic Pallardy
     

01 Nov, 2016

3 commits


09 Sep, 2016

5 commits