From: Leon Romanovsky <leon@kernel.org>
To: Sai Krishna <saikrishnag@marvell.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, sgoutham@marvell.com,
gakula@marvell.com
Subject: Re: [net-next PATCH] octeontx2-af: Add NIX Errata workaround on CN10K silicon
Date: Sun, 19 Feb 2023 11:17:32 +0200 [thread overview]
Message-ID: <Y/HpLEx3Ebh+IegK@unreal> (raw)
In-Reply-To: <20230217055112.1248842-1-saikrishnag@marvell.com>
On Fri, Feb 17, 2023 at 11:21:12AM +0530, Sai Krishna wrote:
> From: Geetha sowjanya <gakula@marvell.com>
>
> This patch adds workaround for below 2 HW erratas
>
> 1. Due to improper clock gating, NIXRX may free the same
> NPA buffer multiple times.. to avoid this, always enable
> NIX RX conditional clock.
>
> 2. NIX FIFO does not get initialized on reset, if the SMQ
> flush is triggered before the first packet is processed, it
> will lead to undefined state. The workaround to perform SMQ
> flush only if packet count is non-zero in MDQ.
>
> Signed-off-by: Geetha sowjanya <gakula@marvell.com>
> Signed-off-by: Sunil Kovvuri Goutham <sgoutham@marvell.com>
> Signed-off-by: Sai Krishna <saikrishnag@marvell.com>
> ---
> .../net/ethernet/marvell/octeontx2/af/rvu.h | 3 +++
> .../ethernet/marvell/octeontx2/af/rvu_cn10k.c | 18 ++++++++++++++++++
> .../ethernet/marvell/octeontx2/af/rvu_nix.c | 10 ++++++++++
> .../ethernet/marvell/octeontx2/af/rvu_reg.h | 2 ++
> 4 files changed, 33 insertions(+)
Just curious, why aren't these erratas coded as PCI quirks?
Thanks
next prev parent reply other threads:[~2023-02-19 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 5:51 [net-next PATCH] octeontx2-af: Add NIX Errata workaround on CN10K silicon Sai Krishna
2023-02-19 9:17 ` Leon Romanovsky [this message]
2023-02-20 10:50 ` patchwork-bot+netdevbpf
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=Y/HpLEx3Ebh+IegK@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saikrishnag@marvell.com \
--cc=sgoutham@marvell.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;
as well as URLs for NNTP newsgroup(s).