From: "André Draszik" <andre.draszik@linaro.org>
To: Tudor Ambarus <tudor.ambarus@linaro.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, peter.griffin@linaro.org,
willmcvicker@google.com, kernel-team@android.com
Subject: Re: [PATCH] firmware: exynos-acpm: check saved RX before bailing out on empty RX queue
Date: Mon, 24 Mar 2025 15:47:54 +0000 [thread overview]
Message-ID: <8c453ce602ab10e09104184fca5310233a9f67e2.camel@linaro.org> (raw)
In-Reply-To: <20250324-acpm-drained-rx-queue-v1-1-577774335151@linaro.org>
On Mon, 2025-03-24 at 12:35 +0000, Tudor Ambarus wrote:
> When we're polling for responses and get a response that corresponds to
> another request, we save the RX data in order to drain the RX queue.
>
> If the response for the current request is not found in the request's
> iteration of the queue, or if the queue is empty, we must check whether
> the RX data was saved by a previous request when it drained the RX queue.
>
> We failed to check for already saved responses when the queue was empty,
> and requests could time out. Check saved RX before bailing out on empty
> RX queue.
>
> Fixes: a88927b534ba ("firmware: add Exynos ACPM protocol driver")
> Reported-by: André Draszik <andre.draszik@linaro.org>
> Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
> ---
> on top of krzk/for-next
> ---
> drivers/firmware/samsung/exynos-acpm.c | 44 +++++++++++++++++++++++-----------
> 1 file changed, 30 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/firmware/samsung/exynos-acpm.c b/drivers/firmware/samsung/exynos-acpm.c
> index a85b2dbdd9f0d7b1f327f54a0a283e4f32587a98..15e991b99f5a384a299c1baf6b279fc93244bcf2 100644
> --- a/drivers/firmware/samsung/exynos-acpm.c
> +++ b/drivers/firmware/samsung/exynos-acpm.c
> @@ -184,6 +184,29 @@ struct acpm_match_data {
> #define client_to_acpm_chan(c) container_of(c, struct acpm_chan, cl)
> #define handle_to_acpm_info(h) container_of(h, struct acpm_info, handle)
>
> +/**
> + * acpm_get_saved_rx() - get the response if it was already saved.
> + * @achan: ACPM channel info.
> + * @xfer: reference to the transfer to get response for.
> + * @tx_seqnum: xfer TX sequence number.
> + */
> +static void acpm_get_saved_rx(struct acpm_chan *achan,
> + const struct acpm_xfer *xfer, u32 tx_seqnum)
> +{
> + const struct acpm_rx_data *rx_data = &achan->rx_data[tx_seqnum - 1];
> + u32 rx_seqnum;
> +
> + if (!rx_data->response)
> + return;
> +
> + rx_seqnum = FIELD_GET(ACPM_PROTOCOL_SEQNUM, rx_data->cmd[0]);
> +
> + if (rx_seqnum == tx_seqnum) {
To help the casual reader, maybe add a comment to say that this condition is true
if/when the response was received, and before reception rx_seqnum will be == 0,
because acpm_prepare_xfer() clears it - i.e. it is not ever supposed to be any
arbitrary number. It's kinda implied, but a comment like that would make this
more explicit. If I'm getting this all right.
Other that that;
Reviewed-by: André Draszik <andre.draszik@linaro.org>
Tested-by: André Draszik <andre.draszik@linaro.org>
> + memcpy(xfer->rxd, rx_data->cmd, xfer->rxlen);
> + clear_bit(rx_seqnum - 1, achan->bitmap_seqnum);
> + }
> +}
> +
> /**
> * acpm_get_rx() - get response from RX queue.
> * @achan: ACPM channel info.
> @@ -204,15 +227,16 @@ static int acpm_get_rx(struct acpm_chan *achan, const struct acpm_xfer *xfer)
> rx_front = readl(achan->rx.front);
> i = readl(achan->rx.rear);
>
> - /* Bail out if RX is empty. */
> - if (i == rx_front)
> + tx_seqnum = FIELD_GET(ACPM_PROTOCOL_SEQNUM, xfer->txd[0]);
> +
> + if (i == rx_front) {
> + acpm_get_saved_rx(achan, xfer, tx_seqnum);
> return 0;
> + }
>
> base = achan->rx.base;
> mlen = achan->mlen;
>
> - tx_seqnum = FIELD_GET(ACPM_PROTOCOL_SEQNUM, xfer->txd[0]);
> -
> /* Drain RX queue. */
> do {
> /* Read RX seqnum. */
> @@ -259,16 +283,8 @@ static int acpm_get_rx(struct acpm_chan *achan, const struct acpm_xfer *xfer)
> * If the response was not in this iteration of the queue, check if the
> * RX data was previously saved.
> */
> - rx_data = &achan->rx_data[tx_seqnum - 1];
> - if (!rx_set && rx_data->response) {
> - rx_seqnum = FIELD_GET(ACPM_PROTOCOL_SEQNUM,
> - rx_data->cmd[0]);
> -
> - if (rx_seqnum == tx_seqnum) {
> - memcpy(xfer->rxd, rx_data->cmd, xfer->rxlen);
> - clear_bit(rx_seqnum - 1, achan->bitmap_seqnum);
> - }
> - }
> + if (!rx_set)
> + acpm_get_saved_rx(achan, xfer, tx_seqnum);
>
> return 0;
> }
>
> ---
> base-commit: f0dbe0d40d08199109cb689849877694a8b91033
> change-id: 20250324-acpm-drained-rx-queue-ec316d4cbcdf
>
> Best regards,
next prev parent reply other threads:[~2025-03-24 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 12:35 Tudor Ambarus
2025-03-24 15:47 ` André Draszik [this message]
2025-04-07 6:46 ` Krzysztof Kozlowski
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=8c453ce602ab10e09104184fca5310233a9f67e2.camel@linaro.org \
--to=andre.draszik@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=kernel-team@android.com \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.com \
/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
all inboxes | Powered by JetHome®