From: Arnaud POULIQUEN <arnaud.pouliquen@foss.st.com>
To: Deepak Kumar Singh <quic_deesin@quicinc.com>,
<bjorn.andersson@linaro.org>, <swboyd@chromium.org>,
<quic_clew@quicinc.com>, <mathieu.poirier@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-remoteproc@vger.kernel.org>
Subject: Re: [PATCH V2 0/3] rpmsg and glink signaling API support
Date: Mon, 25 Apr 2022 10:59:45 +0200 [thread overview]
Message-ID: <c3e080e8-d070-ef90-cd8a-6d4bd41e32e0@foss.st.com> (raw)
In-Reply-To: <5cde9477-d73c-03c4-4dc0-c63fa0f8c8d9@foss.st.com>
Hi,
On 3/23/22 11:17, Arnaud POULIQUEN wrote:
> Hi all,
>
> On 1/18/22 20:43, Deepak Kumar Singh wrote:
>> [Change from V1]
>> Fixed most of the review comments in V1.
>
> This implementation works for the glink transport,
> But how to manage such flow control for other transport
> layer?
> From my POV it is important that it is also usable for
> by transport backends which doe not have such signaling.
> The idea here is not to implement in other backends yet, but
> at least to determine how it could be handled to avoid that
> tomorrow this has to be reworked.
FYI, I've started some dev, trying to adapt the implementation to
the virtio backend to move forward with this topic.
It is only a POC for time being based on a new ROPMsg service for the
flow control.
Linux code is available here:
https://github.com/arnopo/linux/commits/signalling
openamp library associated code is available here:
https://github.com/arnopo/open-amp/commits/flow_ctrl
I hope to find some time next month to continue my dev and send patches
to the mailing list.
Regards,
Arnaud
>
> More than that I wonder if the flow control could also be used
> to solve the RPmsg protocol issue related to the channel
> announcement [1][2]
>
> [1] https://github.com/OpenAMP/open-amp/pull/160
> [2] https://lore.kernel.org/lkml/20220316153001.662422-1-arnaud.pouliquen@foss.st.com/
>
> Thanks,
> Arnaud
>
>>
>> Deepak Kumar Singh (3):
>> rpmsg: core: Add signal API support
>> rpmsg: glink: Add support to handle signals command
>> rpmsg: char: Add TIOCMGET/TIOCMSET ioctl support
>>
>> drivers/rpmsg/qcom_glink_native.c | 77 +++++++++++++++++++++++++++++++++++++++
>> drivers/rpmsg/rpmsg_char.c | 47 ++++++++++++++++++++++--
>> drivers/rpmsg/rpmsg_core.c | 21 +++++++++++
>> drivers/rpmsg/rpmsg_internal.h | 2 +
>> include/linux/rpmsg.h | 14 +++++++
>> 5 files changed, 157 insertions(+), 4 deletions(-)
>>
prev parent reply other threads:[~2022-04-25 9:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 19:43 [PATCH V2 0/3] rpmsg and glink signaling API support Deepak Kumar Singh
2022-01-18 19:43 ` [PATCH V2 1/3] rpmsg: core: Add signal " Deepak Kumar Singh
2022-03-11 21:11 ` Bjorn Andersson
2022-03-23 10:57 ` Arnaud POULIQUEN
2022-03-29 11:00 ` Deepak Kumar Singh
2022-04-01 13:23 ` Arnaud POULIQUEN
2022-01-18 19:43 ` [PATCH V2 2/3] rpmsg: glink: Add support to handle signals command Deepak Kumar Singh
2022-03-11 21:09 ` Bjorn Andersson
2022-03-23 7:20 ` Deepak Kumar Singh
2022-04-01 13:27 ` Arnaud POULIQUEN
2022-01-18 19:43 ` [PATCH V2 3/3] rpmsg: char: Add TIOCMGET/TIOCMSET ioctl support Deepak Kumar Singh
2022-03-23 13:38 ` Arnaud POULIQUEN
2022-03-29 12:25 ` Deepak Kumar Singh
2022-04-01 13:54 ` Arnaud POULIQUEN
2022-03-23 10:17 ` [PATCH V2 0/3] rpmsg and glink signaling API support Arnaud POULIQUEN
2022-04-25 8:59 ` Arnaud POULIQUEN [this message]
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=c3e080e8-d070-ef90-cd8a-6d4bd41e32e0@foss.st.com \
--to=arnaud.pouliquen@foss.st.com \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=quic_clew@quicinc.com \
--cc=quic_deesin@quicinc.com \
--cc=swboyd@chromium.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox