From: Hari Prasath G E <gehariprasath@ti.com>
To: Siddharth Vadapalli <s-vadapalli@ti.com>, <nm@ti.com>,
<ssantosh@kernel.org>
Cc: <stable@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <srk@ti.com>,
<s-adivi@ti.com>
Subject: Re: [PATCH] soc: ti: k3-ringacc: Fix access mode for k3_ringacc_ring_pop_tail_io()
Date: Tue, 21 Apr 2026 21:20:56 +0530 [thread overview]
Message-ID: <d36239c2-98d5-4e5b-b99e-470f4d753a52@ti.com> (raw)
In-Reply-To: <20260413065125.627180-1-s-vadapalli@ti.com>
Hello Siddharth,
Thanks for the patch.
On 4/13/2026 12:21 PM, Siddharth Vadapalli wrote:
> k3_ringacc_ring_pop_tail_io() invokes k3_ringacc_ring_access_io() with the
> access mode incorrectly set to K3_RINGACC_ACCESS_MODE_POP_HEAD instead of
> K3_RINGACC_ACCESS_MODE_POP_TAIL. Fix this.
>
> Fixes: 3277e8aa2504 ("soc: ti: k3: add navss ringacc driver")
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
> ---
>
> Hello,
>
> This patch is based on commit
> 028ef9c96e96 Linux 7.0
> of Mainline Linux.
>
> I noticed (visually) the incorrect access mode while working on:
> https://lore.kernel.org/r/20260325123850.638748-1-s-vadapalli@ti.com/
>
> Regards,
> Siddharth.
>
> drivers/soc/ti/k3-ringacc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/soc/ti/k3-ringacc.c b/drivers/soc/ti/k3-ringacc.c
> index 7602b8a909b0..24f658e8c1dc 100644
> --- a/drivers/soc/ti/k3-ringacc.c
> +++ b/drivers/soc/ti/k3-ringacc.c
> @@ -1083,7 +1083,7 @@ static int k3_ringacc_ring_pop_io(struct k3_ring *ring, void *elem)
> static int k3_ringacc_ring_pop_tail_io(struct k3_ring *ring, void *elem)
> {
> return k3_ringacc_ring_access_io(ring, elem,
> - K3_RINGACC_ACCESS_MODE_POP_HEAD);
> + K3_RINGACC_ACCESS_MODE_POP_TAIL);
I see that you have noticed this visually and fixed this,was there any
impact you faced without this change like data corruption or something ?
It would be better to mention the impact this change brings-in by doing
some analysis.
There is a similar function k3_ringacc_ring_pop_tail_proxy() few lines
above where the same change might be required.
Regards,
Hari
> }
>
> /*
next prev parent reply other threads:[~2026-04-21 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 6:51 [PATCH] soc: ti: k3-ringacc: Fix access mode for k3_ringacc_ring_pop_tail_io() Siddharth Vadapalli
2026-04-21 15:50 ` Hari Prasath G E [this message]
2026-04-22 4:54 ` Siddharth Vadapalli
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=d36239c2-98d5-4e5b-b99e-470f4d753a52@ti.com \
--to=gehariprasath@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=s-adivi@ti.com \
--cc=s-vadapalli@ti.com \
--cc=srk@ti.com \
--cc=ssantosh@kernel.org \
--cc=stable@vger.kernel.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