Netdev List
 help / color / mirror / Atom feed
From: Christoph Fritz <chf.fritz@googlemail.com>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: qca_spi: SPI_REG_SIGNATURE sometimes not recognized
Date: Mon, 05 Feb 2024 01:36:00 +0100	[thread overview]
Message-ID: <b7c66e3ea1a87e4dc0edb2df15e29f43fa5bf723.camel@googlemail.com> (raw)
In-Reply-To: <e6c64849-ded6-49e0-aa15-283346b185e4@gmx.net>

> >   working on a board with QCA7005, on probe() SPI_REG_SIGNATURE
> > sometimes fails (~1 out of 5 times) to be recognized correctly, even
> > after multiple reads and retries.

> at the time of writing the driver, i assumed the QCA7000 is always
> powered up (takes ~ 1 second) during probe of the driver and the driver
> could do the signature check during probe. But this doesn't work in all
> cases. So qca_spi driver has the module parameter qcaspi_pluggable,
> which is disabled per default. If you enable this, this will skip the
> signature check during probe and let the spi thread handle the
> synchronization.
> 
> Does this fix your problem?

Yes, thanks - this seems to fix the probe issue.

> Regardless of the results, i think qcaspi_pluggable should be enabled
> per default.

I think so too. Because the current default (off) is only appropriate
when the chip already gets powered up long before probing. This seems
unusual and at the same time understandable because the driver lacks
regulator and gpio-reset handling.

What about removing qcaspi_pluggable completely while adding a warning
when QCASPI_SYNC_UNKNOWN hits way too many times?

Thanks
  -- Christoph


      reply	other threads:[~2024-02-05  0:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-04 21:23 qca_spi: SPI_REG_SIGNATURE sometimes not recognized Christoph Fritz
2024-02-04 21:52 ` Stefan Wahren
2024-02-05  0:36   ` Christoph Fritz [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=b7c66e3ea1a87e4dc0edb2df15e29f43fa5bf723.camel@googlemail.com \
    --to=chf.fritz@googlemail.com \
    --cc=netdev@vger.kernel.org \
    --cc=wahrenst@gmx.net \
    /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