From: Ryosuke Saito <ryosuke.saito@linaro.org>
To: Simon Horman <horms@kernel.org>
Cc: jaswinder.singh@linaro.org, ilias.apalodimas@linaro.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, masahisa.kojima@linaro.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: netsec: replace cpu_relax() with timeout handling for register checks
Date: Mon, 20 Nov 2023 11:19:48 +0900 [thread overview]
Message-ID: <5027002.31r3eYUQgx@fedora> (raw)
In-Reply-To: <20231119185337.GE186930@vergenet.net>
[Resend again after removing an HTML format. Sorry for that.]
Hi Simon-san,
On Mon, Nov 20, 2023 at 3:53 AM Simon Horman <horms@kernel.org> wrote:
>
> On Fri, Nov 17, 2023 at 05:10:02PM +0900, Ryosuke Saito wrote:
> > The cpu_relax() loops have the potential to hang if the specified
> > register bits are not met on condition. The patch replaces it with
> > usleep_range() and netsec_wait_while_busy() which includes timeout
> > logic.
> >
> > Additionally, if the error condition is met during interrupting DMA
> > transfer, there's no recovery mechanism available. In that case, any
> > frames being sent or received will be discarded, which leads to
> > potential frame loss as indicated in the comments.
> >
> > Signed-off-by: Ryosuke Saito <ryosuke.saito@linaro.org>
> > ---
> > drivers/net/ethernet/socionext/netsec.c | 35 ++++++++++++++++---------
> > 1 file changed, 23 insertions(+), 12 deletions(-)
>
> ...
>
> > @@ -1476,9 +1483,13 @@ static int netsec_reset_hardware(struct netsec_priv
*priv,
> > netsec_write(priv, NETSEC_REG_DMA_MH_CTRL, MH_CTRL__MODE_TRANS);
> > netsec_write(priv, NETSEC_REG_PKT_CTRL, value);
> >
> > - while ((netsec_read(priv, NETSEC_REG_MODE_TRANS_COMP_STATUS) &
> > - NETSEC_MODE_TRANS_COMP_IRQ_T2N) == 0)
> > - cpu_relax();
> > + usleep_range(100000, 120000);
> > +
> > + if ((netsec_read(priv, NETSEC_REG_MODE_TRANS_COMP_STATUS) &
> > + NETSEC_MODE_TRANS_COMP_IRQ_T2N) == 0) {
> > + dev_warn(priv->dev,
> > + "%s: trans comp timeout.\n", __func__);
> > + }
>
> Hi Saito-san,
>
> could you add some colour to how the new code satisfies the
> requirements of the hardware? In particular, the use of
> usleep_range(), and the values passed to it.
For the h/w requirements, I followed U-Boot upstream:
https://elixir.bootlin.com/u-boot/latest/source/drivers/net/sni_netsec.c
It has the same function as well, netsec_reset_hardware(), and the
corresponding potion is the following read-check loop:
1012 value = 100;
1013 while ((netsec_read_reg(priv, NETSEC_REG_MODE_TRANS_COMP_STATUS)
&
1014 NETSEC_MODE_TRANS_COMP_IRQ_T2N) == 0) {
1015 udelay(1000);
1016 if (--value == 0) {
1017 value = netsec_read_reg(priv,
NETSEC_REG_MODE_TRANS_COMP_STATUS);
1018 pr_err("%s:%d timeout! val=%x\n", __func__,
__LINE__, value);
1019 break;
1020 }
1021 }
The maximum t/o = 1000us * 100 + read time
Regards,
Ryo
next prev parent reply other threads:[~2023-11-20 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 8:10 [PATCH] net: netsec: replace cpu_relax() with timeout handling for register checks Ryosuke Saito
2023-11-19 18:53 ` Simon Horman
2023-11-20 2:19 ` Ryosuke Saito [this message]
2023-11-21 11:02 ` Simon Horman
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=5027002.31r3eYUQgx@fedora \
--to=ryosuke.saito@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=jaswinder.singh@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahisa.kojima@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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