netdev - wfx200 weird out-of-range power supply issue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250605134034.GD1779@bender.k.g>
Date: Thu, 5 Jun 2025 16:40:34 +0300
From: Petko Manolov <petko.manolov@...sulko.com>
To: netdev@...r.kernel.org
Cc: Jerome.Pouiller@...abs.com, David.Legoff@...abs.com
Subject: wfx200 weird out-of-range power supply issue

	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.

thanks guys,
Petko