wlan 8890 suspend/resume issue

[Mike17]

Hi 

I use MTK chip as host and when I try to suspend the system and resume the system

I'll got the following error

[ 401.776851] <1>.(1)[0:swapper/1]wlan_wakeup_card_timeout_func: ps_state=3

[ 401.783738] <1>.(1)[0:swapper/1]mmlan0:
[ 401.783740] <1>.(1)[0:swapper/1]Wakeup card timeout!
[ 401.784912] <1>.(1)[0:swapper/1]Driver version = PCIE9098--17.68.1.p71.3-MXM5X17265.p1-GPL-(FP68)
[ 401.786053] <1>.(1)[0:swapper/1]main_state = 4
[ 401.786632] <1>.(1)[0:swapper/1]ioctl_pending = 2

[ 401.794808] <1>.(1)[0:swapper/1]Media state = "Disconnected"

Does anyone know how to fix this issue?

[Mike17]

@estephania_mart 

thanks, i will ask azurewave to help to download the lastest FW

BTW, after host enter suspend state, the AP will be stop. Is it normal?

[ 394.598647] <3>.(3)[65:kworker/u8:2]PM: suspend entry (deep)

[ 394.598647] <3>.(3)[65:kworker/u8:2]PM: suspend entry (deep)
[ 394.599396] <3>.(3)[65:kworker/u8:2]PM: Syncing filesystems ... done.
[ 394.653255] <3>.(3)[65:kworker/u8:2]charger_pm_event: enter PM_SUSPEND_PREPARE
[ 394.654204] <3>.(3)[65:kworker/u8:2][name:spm&][SPM] PM: suspend entry 2021-12-21 02:11:34.008715713 UTC
[ 394.654212] <3>.(3)[65:kworker/u8:2]Freezing user space processes ... (elapsed 0.010 seconds) done.
[ 394.665528] <3>.(3)[65:kworker/u8:2]OOM killer disabled.
[ 394.666201] <3>.(3)[65:kworker/u8:2]Freezing remaining freezable tasks ... (elapsed 0.004 seconds) done.
[ 394.674721] <3>.(3)[720:kworker/u8:3]wlan: Stoping AP
[ 394.675766] <3>.(3)[720:kworker/u8:3]wlan: AP stopped
[ 394.676639] <2>.(2)[15840:kworker/u8:4]wlan: Stoping AP

[estephania_mart]

hello,

Could you please help me with more details on the hardware setup you are using ?

Regards,

Estephania

[Mike17]

Hi 

I use AzureWave module(the model is AW-XM458) and the communication interface between host(I use MTK chip) and module is PCIE.

I configure the drive to uAP mode

thanks

[estephania_mart]

Hello,

By any chance , in the configuration of your device did you enable the interface for the module? The device does not seem to find the module so it can start it up according to the log you share

Regards,
Estephania

[Mike17]

Hi 

when the host from bootup to run, it seems wifi is working

Is there anyway to fix this issue

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2021.12.21 11:27:17 =~=~=~=~=~=~=~=~=~=~=~=
rch_sync_cache_range: addr[0x60000000], size[0x10000000]
get limit and align weak func
u64 mblock_alloc(u64, u64, u64, u64, u32, const char *):421: start: 0x7e000000, sz: 0x500000 map:0 name:md_smem_ncache
ccci_request_named_mem: ret = 0 no error
mblock_alloc(sz=0x500000, ali=0x2000000, lim=0x90000000, exp=0x0, name=md_smem_ncache)=>0x7e000000,0x40210000
env[apmd1_smem]0.
smem_info.base_addr: 0x7e000000

 4339: [ 40.294223] <1>.(1)[6089:kworker/u9:3]wlan: SCAN COMPLETED: scanned AP count=11
4340: [ 40.643529] <3>.(3)[422:kworker/u9:0]wlan: SCAN COMPLETED: scanned AP count=17
4352: [ 40.984233] <0>.(0)[422:kworker/u9:0]wlan: SCAN COMPLETED: scanned AP count=9
4355: [ 41.028720] <1>.(1)[13082:hostapd]wlan: Starting AP
4363: [ 41.036867] <1>.(2)[13082:hostapd]wlan: AP started
4367: [ 41.039014] <2>.(2)[13082:hostapd]wlan: HostMlme uap0 send deauth/disassoc

But after system come back to run state from suspend state , the wifi seems to be sleep state

[ 397.509338] <0>-(0)[65:kworker/u8:2]PM: Calling cpu_pm_resume+0x0/0x20
[ 397.509338] <0>-(0)[65:kworker/u8:2]PM: Calling clkdbg_syscore_resume+0x0/0x18

[ 401.776851] <1>.(1)[0:swapper/1]wlan_wakeup_card_timeout_func: ps_state=3
[ 401.783738] <1>.(1)[0:swapper/1]mmlan0:
[ 401.783740] <1>.(1)[0:swapper/1]Wakeup card timeout!
[ 401.784912] <1>.(1)[0:swapper/1]Driver version = PCIE9098--17.68.1.p71.3-MXM5X17265.p1-GPL-(FP68)
[ 401.786053] <1>.(1)[0:swapper/1]main_state = 4
[ 401.786632] <1>.(1)[0:swapper/1]ioctl_pending = 2
[ 401.787307] <1>.(1)[0:swapper/1]tx_pending = 0
[ 401.787886] <1>.(1)[0:swapper/1]wmm_tx_pending[0] = 0
[ 401.788540] <1>.(1)[0:swapper/1]wmm_tx_pending[1] = 0
[ 401.789192] <1>.(1)[0:swapper/1]wmm_tx_pending[2] = 0
[ 401.789845] <1>.(1)[0:swapper/1]wmm_tx_pending[3] = 0
[ 401.790499] <1>.(1)[0:swapper/1]rx_pending = 0
[ 401.791075] <1>.(1)[0:swapper/1]lock_count = 45
[ 401.791662] <1>.(1)[0:swapper/1]malloc_count = 49
[ 401.792273] <1>.(1)[0:swapper/1]mbufalloc_count = 136
[ 401.792926] <1>.(1)[0:swapper/1]malloc_cons_count = 4
[ 401.793578] <1>.(1)[0:swapper/1]hs_skip_count = 0
[ 401.794188] <1>.(1)[0:swapper/1]hs_force_count = 0
[ 401.794808] <1>.(1)[0:swapper/1]Media state = "Disconnected"
[ 401.795536] <1>.(1)[0:swapper/1]carrier off

[estephania_mart]

Hello,

Could you please help me check that the definition for the wake-up signals is accroding to this AN ?

https://www.nxp.com/docs/en/application-note/AN13049.pdf

Regards,

[Mike17]

Hi 

I check the signal for this wakeup, but it keeps high when the host enters suspend state and comes back to the running state. After checking the PCIE spec. (5.3.3.2. Link Wakeup),  There are two defined wakeup mechanisms:Beacon and WAKE#.

The Beacon mechanism uses in-band signaling to implement wakeup functionality. The WAKE# mechanism uses sideband signaling to implement wakeup functionality.WAKE# is an “open drain” signal asserted by components requesting wakeup

Do you mean that NXP wlan need to assert this signal or by host ?

[estephania_mart]

Hello,

After checking the driver that you are using seem to be old, could you please help us using the latest one ?

Also, for the wake up function please have a 0 ohm stuff option to connect to GPIO 12(default) or GPIO 13 to M.2 Pin 40. And for the AN13409 to define M.2 Pin 23, 54 and 56

Regards,

[Alexis_A]

Hello @Mike17,

This case would be handled internally and the resolution would be posted in this thread.

BR,

Alexis Andalon