From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Arnaud POULIQUEN <arnaud.pouliquen@foss.st.com>
Cc: Deepak Kumar Singh <quic_deesin@quicinc.com>,
bjorn.andersson@linaro.org, swboyd@chromium.org,
quic_clew@quicinc.com, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH V3 0/3] rpmsg signaling/flowcontrol patches
Date: Mon, 19 Sep 2022 14:15:01 -0600 [thread overview]
Message-ID: <20220919201501.GD759648@p14s> (raw)
In-Reply-To: <74224354-8543-559b-240b-0eda4d68fc52@foss.st.com>
On Wed, Sep 14, 2022 at 09:50:48AM +0200, Arnaud POULIQUEN wrote:
> Hi Deepak,
>
> On 9/14/22 07:24, Deepak Kumar Singh wrote:
> > [Changes from V2]:
> > Trivial review comment fixes.
> > Avoid TIOCM_DTR etc signals in glink layer, use native signal macros only.
> > Glink layer to provide only flowcontrol on/off interface, no specific signal passing/receiving to client.
>
>
> Please, could you have a look to my series that implements
> your proposed interface for the virtio rpmsg [1]?
> It would be nice that your API takes into account update to
> support of the rpmsg virtio implementation proposed in [08/10] rpmsg: Add the
> destination address in rpmsg_set_flow_control[2]
I agree with Arnaud - I would like to see more convergence on this topic. I will
not move forward with this patchset until comments have been provided for [1].
>
> Thanks,
> Arnaud
>
> [1] https://lore.kernel.org/lkml/e54bcfcb-8e37-9caa-b330-a7411820b7ce@foss.st.com/T/
> [2]https://lore.kernel.org/lkml/e54bcfcb-8e37-9caa-b330-a7411820b7ce@foss.st.com/T/#m7340a8e70fb0d8935869c4cef96863abda555c96
>
> >
> > 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 | 63 +++++++++++++++++++++++++++++++++++++++
> > drivers/rpmsg/rpmsg_char.c | 60 ++++++++++++++++++++++++++++++++-----
> > drivers/rpmsg/rpmsg_core.c | 20 +++++++++++++
> > drivers/rpmsg/rpmsg_internal.h | 2 ++
> > include/linux/rpmsg.h | 15 ++++++++++
> > 5 files changed, 152 insertions(+), 8 deletions(-)
> >
next prev parent reply other threads:[~2022-09-19 20:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 5:24 [PATCH V3 0/3] rpmsg signaling/flowcontrol patches Deepak Kumar Singh
2022-09-14 5:25 ` [PATCH V3 1/3] rpmsg: core: Add signal API support Deepak Kumar Singh
2022-09-14 5:25 ` [PATCH V3 2/3] rpmsg: glink: Add support to handle signals command Deepak Kumar Singh
2022-11-02 3:25 ` Bjorn Andersson
2022-09-14 5:25 ` [PATCH V3 3/3] rpmsg: char: Add TIOCMGET/TIOCMSET ioctl support Deepak Kumar Singh
2022-11-02 3:30 ` Bjorn Andersson
2022-09-14 7:50 ` [PATCH V3 0/3] rpmsg signaling/flowcontrol patches Arnaud POULIQUEN
2022-09-19 20:15 ` Mathieu Poirier [this message]
2022-11-02 3:32 ` Bjorn Andersson
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=20220919201501.GD759648@p14s \
--to=mathieu.poirier@linaro.org \
--cc=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=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;
as well as URLs for NNTP newsgroup(s).