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

On 25-06-06 16:42:42, Jérôme Pouiller wrote:
> 
> 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? 

Yes, this turned out to be the case.  Now the chip appears to be powered up and i
get nice and very promising:

[   33.960683] wfx-spi spi0.0: started firmware 3.17.0 "WF200_ASIC_WFM_(Jenkins)_FW3.17.0" (API: 3.12, keyset: C0, caps: 0x00000000)                                               
[   33.991401] wfx-spi spi0.0: sending configuration file wfx/wf200.pds                                                                                                            
[   34.006885] wfx-spi spi0.0: enable 'quiescent' power mode with wakeup GPIO and PDS file wfx/wf200.pds
[   34.007212] wfx-spi spi0.0: MAC address 0: 84:fd:27:71:72:f7                          
[   34.011703] wfx-spi spi0.0: MAC address 1: 84:fd:27:71:72:f8
[   34.045198] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'

However, when i do "ip link set dev wlan0 up" i get:

[  118.481024] wfx-spi spi0.0: timeout while wake up chip             
[  118.501051] wfx-spi spi0.0: timeout while wake up chip        
[  118.521142] wfx-spi spi0.0: timeout while wake up chip            
[  118.541059] wfx-spi spi0.0: max wake-up retries reached   

Could this be an issue with:

"enable 'quiescent' power mode with wakeup GPIO and PDS file wfx/wf200.pds"

from the kernel log?


thanks,
Petko

      parent reply	other threads:[~2025-06-24 18:10 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
2025-06-10 14:55       ` Petko Manolov
2025-06-24 18:09       ` Petko Manolov [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=20250624180958.GC9115@cabron.k.g \
    --to=petko.manolov@konsulko.com \
    --cc=David.Legoff@silabs.com \
    --cc=jerome.pouiller@silabs.com \
    --cc=netdev@vger.kernel.org \
    /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.