Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ 16.922685] wfx-sdio mmc1:0001:1: timeout while wake up chip #4

Open
avijitnsec opened this issue Aug 9, 2024 · 4 comments
Open

Comments

@avijitnsec
Copy link

We are using the wfx200 driver for 2 devices.

We are creating AP at one, connecting to that AP from the other one (wpa). We are observing that every time we try to connect to the AP, it is showing us the warning message "[ 16.922685] wfx-sdio mmc1:0001:1: timeout while wake up chip". Can we keep the wake-up gpio ON all the time ? How to safely do that ?

@jerome-pouiller
Copy link
Collaborator

Hello @avijitnsec,

Normally, this issue is fixed since firmware 3.9. Can you check what firmware are you using?

That's said, the warning is normally harmless. The workaround implemented in the driver allow to work with any firmware version.

If you don't care about power consumption, you can ask to the chip to ignore the wake-up signal. You just have to remove declaration of the wakeup-gpios in your Device Tree.

@jerome-pouiller
Copy link
Collaborator

It seems some users have reported in the past this trace was also displayed if some latencies (>6ms) happen while accessing to SDIO bus.

In this case, the cause may just be high CPU usage.

It is harmless.

@avijitnsec
Copy link
Author

We are trying to assign dhcp using udhcpc. Looking into dmesg log, when udhcpc is struggling to get an IP address, it looks like there is multiple retries in the background as well as an error message from wfx-sdio with vif 0.
image
Tracing it to the code this is what we have found
image

I feel like this is related to this. Can you please comment?

@jerome-pouiller
Copy link
Collaborator

The WF200 does not receive any response from the AP. This happen early during the connection (before DHCP, even before authentication). Can you confirm you see this AP with a sane RSSI in scan results? Are you using the "combo mode" (two vifs on the same wf200)?

(I think the code you underlying is not related to your issue)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants