From: Simon Horman <simon.horman@corigine.com>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Stefan Wahren <stefan.wahren@chargebyte.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net resend] net: qca_spi: Avoid high load if QCA7000 is not available
Date: Thu, 15 Jun 2023 09:53:16 +0200 [thread overview]
Message-ID: <ZIrDbJzbBaYeCLUz@corigine.com> (raw)
In-Reply-To: <3452498b-b89c-c72d-d196-950520ed8c50@i2se.com>
On Wed, Jun 14, 2023 at 10:40:57PM +0200, Stefan Wahren wrote:
> Hi Simon,
>
> Am 14.06.23 um 18:58 schrieb Simon Horman:
> > On Wed, Jun 14, 2023 at 01:17:14PM +0200, Stefan Wahren wrote:
> > > In case the QCA7000 is not available via SPI (e.g. in reset),
> > > the driver will cause a high load. The reason for this is
> > > that the synchronization is never finished and schedule()
> > > is never called. Since the synchronization is not timing
> > > critical, it's safe to drop this from the scheduling condition.
> > >
> > > Signed-off-by: Stefan Wahren <stefan.wahren@chargebyte.com>
> > > Fixes: 291ab06ecf67 ("net: qualcomm: new Ethernet over SPI driver for
> > > QCA7000")
> >
> > Hi Stefan,
> >
> > the Fixes should be on a single line.
> >
> > Fixes: 291ab06ecf67 ("net: qualcomm: new Ethernet over SPI driver for QCA7000")
>
> thanks for pointing out. Unfortunately this comes from the mail server,
> which line warp here. I will try to use a different account. Sorry about
> this mess :-(
Thanks Stefan,
I thought it might be something annoying like that.
I see v2 and it seems clean wrt the issues I've raised here :)
>
> >
> > > ---
> > > drivers/net/ethernet/qualcomm/qca_spi.c | 3 +--
> > > 1 file changed, 1 insertion(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/net/ethernet/qualcomm/qca_spi.c
> > > b/drivers/net/ethernet/qualcomm/qca_spi.c
> >
> > Likewise, the above two lines should be a single line.
> > Unfortunately it seems that because it is not git doesn't apply
> > this patch, which creates problems for automation linked to patchwork.
> >
> > I think it would be best to repost after resolving these minor issues.
> >
> > > index bba1947792ea16..90f18ea4c28ba1 100644
> > > --- a/drivers/net/ethernet/qualcomm/qca_spi.c
> > > +++ b/drivers/net/ethernet/qualcomm/qca_spi.c
> > > @@ -582,8 +582,7 @@ qcaspi_spi_thread(void *data)
> > > while (!kthread_should_stop()) {
> > > set_current_state(TASK_INTERRUPTIBLE);
> > > if ((qca->intr_req == qca->intr_svc) &&
> > > - (qca->txr.skb[qca->txr.head] == NULL) &&
> > > - (qca->sync == QCASPI_SYNC_READY))
> > > + !qca->txr.skb[qca->txr.head])
> > > schedule();
> > > set_current_state(TASK_RUNNING);
> > >
> >
prev parent reply other threads:[~2023-06-15 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 11:17 [PATCH net resend] net: qca_spi: Avoid high load if QCA7000 is not available Stefan Wahren
2023-06-14 16:58 ` Simon Horman
2023-06-14 20:40 ` Stefan Wahren
2023-06-15 7:53 ` Simon Horman [this message]
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=ZIrDbJzbBaYeCLUz@corigine.com \
--to=simon.horman@corigine.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefan.wahren@chargebyte.com \
--cc=stefan.wahren@i2se.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).