All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jérôme Pouiller" <jerome.pouiller@silabs.com>
To: Petko Manolov <petko.manolov@konsulko.com>
Cc: netdev@vger.kernel.org, David.Legoff@silabs.com
Subject: Re: wfx200 weird out-of-range power supply issue
Date: Fri, 06 Jun 2025 16:42:42 +0200	[thread overview]
Message-ID: <3711319.R56niFO833@nb0018864> (raw)
In-Reply-To: <20250606140143.GA3800@carbon.k.g>

On Friday 6 June 2025 16:01:43 CEST Petko Manolov wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
> 
> 
> On 25-06-06 14:13:18, Jérôme Pouiller wrote:
> > On Thursday 5 June 2025 15:40:34 CEST Petko Manolov wrote:
> > >         Hey guys,
> > >
> > > Apologies if this has been asked before, but i've searched and didn't find
> > > anything related to this problem.  So here it goes: i'm upgrading the kernel of
> > > a custom stm32mp15 board (from v5.4 to v6.6) and i've stumbled upon this when
> > > wfx driver module get loaded:
> > >
> > > wfx-spi spi0.0: sending configuration file wfx/wf200.pds
> > > wfx-spi spi0.0: asynchronous error: out-of-range power supply voltage: -20
> > > ... a bunch of "hif: 00000000: bc 04 e4 15 04 00 00 00 ec 00 74 76 f7 b7 cd 09" like messages ...
> > > wfx-spi spi0.0: time out while polling control register
> > > wfx-spi spi0.0: chip is abnormally long to answer
> > > wfx-spi spi0.0: chip did not answer
> > > wfx-spi spi0.0: hardware request CONFIGURATION (0x09) on vif 2 returned error -110
> > > wfx-spi spi0.0: PDS:4: chip didn't reply (corrupted file?)
> > > wfx-spi: probe of spi0.0 failed with error -110
> > >
> > > Needless to say that v5.4 kernel setup works fine.  The only difference with
> > > v6.6 is the wfx driver and kernel's DTB.  Now, i've verified that wf200 is
> > > powered with 3.3V, in both cases, so that's not it.  I've also lowered the SPI
> > > clock from 40000000 to 20000000 but it didn't make a difference.
> > >
> > > By looking at the driver i'm fairly certain the above error is actually coming
> > > from the wf200 firmware and the driver is just printing an error message so i
> > > don't see reasonable ways of debugging this thing.  In short, any suggestion
> > > would be greatly appreciated.
> >
> > I believe you should have a trace with the firmware version (starting with
> > "started firmware x.x.x"). Could you provide the firmware versions?
> 
> Here's what i get with the new firmware:
> 
> wfx-spi spi0.0: started firmware 3.17.0 "WF200_ASIC_WFM_(Jenkins)_FW3.17.0" (API: 3.12, keyset: C0, caps: 0x00000000)
> wfx-spi spi0.0: sending configuration file wfx/wf200.pds
> wfx-spi spi0.0: asynchronous error: out-of-range power supply voltage: -20
> 
> This is with the old one:
> 
> wfx-spi spi0.0: started firmware 3.12.2 "WF200_ASIC_WFM_(Jenkins)_FW3.12.2" (API: 3.7, keyset: C0, caps: 0x00000000)
> wfx-spi spi0.0: sending configuration file wfx/wf200.pds
> wfx-spi spi0.0: asynchronous error: out-of-range power supply voltage: -21
> 
> Apart from the error number the rest is pretty much the same.  Both dumps from
> using wf200-v6.6.pds (attached) as the old .pds won't load on v6.6.
> 
> > The issue appears when the driver load the wf200.pds. Can you provide
> > the wf200.pds you used with 5.4 and with 6.6? Normally, you can't use
> > the same file since the format has changed in v5.17.
> 
> Attached you'll find both, old and new, versions of the PDS.  This is what i
> used to generate the v6.6 version:
> 
> pds_compress -l BRD8023A_Rev_B01.pds.in wf200-v6.6.pds
> 
> The old one used '-p' instead of '-l', but this is due to the format change, as
> you mentioned above.

Things are going to start to become fun. Your wf200-v6.6.pds is exactly the
same (same md5sum) than the one I use for ages. So the issue is not on this
side.

For info, I have a setup with kernel 6.1 + firmware 3.16.0 + Raspberry Pi
here.

Do you think your power supply could be unstable with your new DT? 

The voltage values reported by the driver (-21 and -20) are obviously not
correct. Maybe it would make sense to get the real value measured by the
chip. Do you have access to official Silabs support to make that request?




-- 
Jérôme Pouiller



  reply	other threads:[~2025-06-06 15:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 13:40 wfx200 weird out-of-range power supply issue Petko Manolov
2025-06-06 12:13 ` Jérôme Pouiller
2025-06-06 14:01   ` Petko Manolov
2025-06-06 14:42     ` Jérôme Pouiller [this message]
2025-06-10 14:55       ` Petko Manolov
2025-06-24 18:09       ` Petko Manolov

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=3711319.R56niFO833@nb0018864 \
    --to=jerome.pouiller@silabs.com \
    --cc=David.Legoff@silabs.com \
    --cc=netdev@vger.kernel.org \
    --cc=petko.manolov@konsulko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.