From: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com> To: Bjorn Andersson <bjorn.andersson@linaro.org>, Mathieu Poirier <mathieu.poirier@linaro.org> Cc: <linux-remoteproc@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-stm32@st-md-mailman.stormreply.com>, Deepak Kumar Singh <quic_deesin@quicinc.com>, Chris Lew <quic_clew@quicinc.com>, <arnaud.pouliquen@foss.st.com> Subject: [RFC PATCH 00/10] Introduction of rpmsg flow control service Date: Fri, 20 May 2022 10:29:30 +0200 [thread overview] Message-ID: <20220520082940.2984914-1-arnaud.pouliquen@foss.st.com> (raw) This series proposes an implementation for the rpmsg virtio transport backend, of the signaling API proposed by Deepak Kumar Singh: "rpmsg and glink signaling API support" [1] The aim of the series is to offer the possibility for an endpoint to inform a remote endpoint about its state, based on a software flow control[2]. For this a new rpmsg service( with a fixed address 64) is proposed. It is responsible for: - transmitting local endpoint flow control information to the remote side, - informing a local endpoint about a remote endpoint flow control. For the rpmsg virtio transport layer the service is negotiated thanks to the virtio feature flag: VIRTIO_RPMSG_F_FC Notice that this pull request introduces new feature in the rpmsg protocol, So it has to be aligned with OpenAMP implementation. Pending OpenAMP pull request is available here: https://github.com/OpenAMP/open-amp/pull/394 [1]https://lkml.org/lkml/2022/1/18/867 [2]https://en.wikipedia.org/wiki/Software_flow_control Arnaud Pouliquen (8): rpmsg: core: Add rpmsg device remote flow control announcement ops rpmsg: virtio: Implement the announce_remote_fc ops rpmsg: Introduce flow control channel driver rpmsg: virtio: Add support of the VIRTIO_RPMSG_F_FC feature rpmsg: virtio: Implement the set_flow_control ops rpmsg: Add the destination address in rpmsg_set_flow_control rpmsg: tty : Add the support of the flow control rpmsg: virtio: Set default dst address on flow control Deepak Kumar Singh (2): rpmsg: core: Add signal API support rpmsg: char: Add TIOCMGET/TIOCMSET ioctl support drivers/rpmsg/Kconfig | 11 +++ drivers/rpmsg/Makefile | 1 + drivers/rpmsg/rpmsg_char.c | 56 +++++++++++++-- drivers/rpmsg/rpmsg_core.c | 47 +++++++++++++ drivers/rpmsg/rpmsg_fc.c | 113 +++++++++++++++++++++++++++++++ drivers/rpmsg/rpmsg_internal.h | 9 +++ drivers/rpmsg/virtio_rpmsg_bus.c | 111 +++++++++++++++++++++++++++++- drivers/tty/rpmsg_tty.c | 50 ++++++++++++++ include/linux/rpmsg.h | 15 ++++ include/linux/rpmsg/fc.h | 51 ++++++++++++++ 10 files changed, 456 insertions(+), 8 deletions(-) create mode 100644 drivers/rpmsg/rpmsg_fc.c create mode 100644 include/linux/rpmsg/fc.h -- 2.25.1
next reply other threads:[~2022-05-20 8:31 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-20 8:29 Arnaud Pouliquen [this message] 2022-05-20 8:29 ` [RFC PATCH 01/10] rpmsg: core: Add signal API support Arnaud Pouliquen 2022-05-20 8:29 ` [RFC PATCH 02/10] rpmsg: char: Add TIOCMGET/TIOCMSET ioctl support Arnaud Pouliquen 2022-05-20 8:29 ` [RFC PATCH 03/10] rpmsg: core: Add rpmsg device remote flow control announcement ops Arnaud Pouliquen 2022-05-20 8:29 ` [RFC PATCH 04/10] rpmsg: virtio: Implement the announce_remote_fc ops Arnaud Pouliquen 2022-05-20 8:29 ` [RFC PATCH 05/10] rpmsg: Introduce flow control channel driver Arnaud Pouliquen 2022-05-20 8:29 ` [RFC PATCH 06/10] rpmsg: virtio: Add support of the VIRTIO_RPMSG_F_FC feature Arnaud Pouliquen 2022-05-20 8:29 ` [RFC PATCH 07/10] rpmsg: virtio: Implement the set_flow_control ops Arnaud Pouliquen 2022-05-20 8:29 ` [RFC PATCH 08/10] rpmsg: Add the destination address in rpmsg_set_flow_control Arnaud Pouliquen 2022-05-20 8:29 ` [RFC PATCH 09/10] rpmsg: tty : Add the support of the flow control Arnaud Pouliquen 2022-05-20 8:29 ` [RFC PATCH 10/10] rpmsg: virtio: Set default dst address on " Arnaud Pouliquen 2022-05-24 15:34 ` [RFC PATCH 00/10] Introduction of rpmsg flow control service Mathieu Poirier 2022-05-25 8:57 ` Arnaud POULIQUEN
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220520082940.2984914-1-arnaud.pouliquen@foss.st.com \ --to=arnaud.pouliquen@foss.st.com \ --cc=bjorn.andersson@linaro.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-remoteproc@vger.kernel.org \ --cc=linux-stm32@st-md-mailman.stormreply.com \ --cc=mathieu.poirier@linaro.org \ --cc=quic_clew@quicinc.com \ --cc=quic_deesin@quicinc.com \ --subject='Re: [RFC PATCH 00/10] Introduction of rpmsg flow control service' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).