From: Arnaud POULIQUEN <arnaud.pouliquen@foss.st.com>
To: Sarannya S <quic_sarannya@quicinc.com>,
<quic_bjorande@quicinc.com>, <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>,
Deepak Kumar Singh <quic_deesin@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>
Subject: Re: [PATCH V5 1/3] rpmsg: core: Add signal API support
Date: Wed, 19 Apr 2023 11:53:49 +0200 [thread overview]
Message-ID: <0543735a-5f0c-bdf4-2a89-e94841bd4a68@foss.st.com> (raw)
In-Reply-To: <1681807721-32343-2-git-send-email-quic_sarannya@quicinc.com>
Hi,
On 4/18/23 10:48, Sarannya S wrote:
> From: Deepak Kumar Singh <quic_deesin@quicinc.com>
>
> Some transports like Glink support the state notifications between
> clients using flow control signals similar to serial protocol signals.
> Local glink client drivers can send and receive flow control status
> to glink clients running on remote processors.
>
> Add APIs to support sending and receiving of flow control status by
> rpmsg clients.
>
> Signed-off-by: Deepak Kumar Singh <quic_deesin@quicinc.com>
> Signed-off-by: Sarannya S <quic_sarannya@quicinc.com>
> ---
> drivers/rpmsg/rpmsg_core.c | 20 ++++++++++++++++++++
> drivers/rpmsg/rpmsg_internal.h | 2 ++
> 2 files changed, 22 insertions(+)
>
> diff --git a/drivers/rpmsg/rpmsg_core.c b/drivers/rpmsg/rpmsg_core.c
> index a2207c0..86b4912 100644
> --- a/drivers/rpmsg/rpmsg_core.c
> +++ b/drivers/rpmsg/rpmsg_core.c
> @@ -331,6 +331,24 @@ int rpmsg_trysend_offchannel(struct rpmsg_endpoint *ept, u32 src, u32 dst,
> EXPORT_SYMBOL(rpmsg_trysend_offchannel);
>
> /**
> + * rpmsg_set_flow_control() - sets/clears serial flow control signals
> + * @ept: the rpmsg endpoint
> + * @enable: pause/resume incoming data flow
> + *
> + * Return: 0 on success and an appropriate error value on failure.
> + */
> +int rpmsg_set_flow_control(struct rpmsg_endpoint *ept, bool enable)
Regression since V4[1]
In V4 version the function was:
int rpmsg_set_flow_control(struct rpmsg_endpoint *ept, bool enable, u32 dst)
Following comments on V3 [2]
Without dst parameter it is not compatible with the rpmsg_virtio backend
[1]https://lkml.org/lkml/2022/12/7/506
[2]https://www.spinics.net/lists/kernel/msg4573082.html
Regards
Arnaud
> +{
> + if (WARN_ON(!ept))
> + return -EINVAL;
> + if (!ept->ops->set_flow_control)
> + return -ENXIO;
> +
> + return ept->ops->set_flow_control(ept, enable);
> +}
> +EXPORT_SYMBOL(rpmsg_set_flow_control);
> +
> +/**
> * rpmsg_get_mtu() - get maximum transmission buffer size for sending message.
> * @ept: the rpmsg endpoint
> *
> @@ -539,6 +557,8 @@ static int rpmsg_dev_probe(struct device *dev)
>
> rpdev->ept = ept;
> rpdev->src = ept->addr;
> +
> + ept->flow_cb = rpdrv->flowcontrol;
> }
>
> err = rpdrv->probe(rpdev);
> diff --git a/drivers/rpmsg/rpmsg_internal.h b/drivers/rpmsg/rpmsg_internal.h
> index 39b646d..4fea45a 100644
> --- a/drivers/rpmsg/rpmsg_internal.h
> +++ b/drivers/rpmsg/rpmsg_internal.h
> @@ -55,6 +55,7 @@ struct rpmsg_device_ops {
> * @trysendto: see @rpmsg_trysendto(), optional
> * @trysend_offchannel: see @rpmsg_trysend_offchannel(), optional
> * @poll: see @rpmsg_poll(), optional
> + * @set_flow_control: see @rpmsg_set_flow_control(), optional
> * @get_mtu: see @rpmsg_get_mtu(), optional
> *
> * Indirection table for the operations that a rpmsg backend should implement.
> @@ -75,6 +76,7 @@ struct rpmsg_endpoint_ops {
> void *data, int len);
> __poll_t (*poll)(struct rpmsg_endpoint *ept, struct file *filp,
> poll_table *wait);
> + int (*set_flow_control)(struct rpmsg_endpoint *ept, bool enable);
> ssize_t (*get_mtu)(struct rpmsg_endpoint *ept);
> };
>
next prev parent reply other threads:[~2023-04-19 9:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 8:48 [PATCH V5 0/3] rpmsg signaling/flowcontrol patches Sarannya S
2023-04-18 8:48 ` [PATCH V5 1/3] rpmsg: core: Add signal API support Sarannya S
2023-04-19 9:53 ` Arnaud POULIQUEN [this message]
2023-04-19 20:37 ` Bjorn Andersson
2023-04-18 8:48 ` [PATCH V5 2/3] rpmsg: glink: Add support to handle signals command Sarannya S
2023-04-18 8:48 ` [PATCH V5 3/3] rpmsg: char: Add RPMSG GET/SET SIGNAL IOCTL support Sarannya S
2023-04-19 9:55 ` Arnaud POULIQUEN
2023-04-18 16:09 ` [PATCH V5 0/3] rpmsg signaling/flowcontrol patches Bjorn Andersson
-- strict thread matches above, loose matches on Subject: below --
2023-02-21 16:03 Sarannya S
2023-02-21 16:03 ` [PATCH V5 1/3] rpmsg: core: Add signal API support Sarannya S
2023-02-21 15:55 [PATCH V5 0/3] rpmsg signaling/flowcontrol patches Sarannya S
2023-02-21 15:56 ` [PATCH V5 1/3] rpmsg: core: Add signal API support Sarannya S
2023-02-21 14:35 [PATCH V5 0/3] rpmsg signaling/flowcontrol patches Sarannya S
[not found] ` <1676990114-1369-2-git-send-email-quic_sarannya@quicinc.com>
2023-02-21 17:20 ` [PATCH V5 1/3] rpmsg: core: Add signal API support 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=0543735a-5f0c-bdf4-2a89-e94841bd4a68@foss.st.com \
--to=arnaud.pouliquen@foss.st.com \
--cc=andersson@kernel.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_bjorande@quicinc.com \
--cc=quic_clew@quicinc.com \
--cc=quic_deesin@quicinc.com \
--cc=quic_sarannya@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