Bug 215775

Summary:	ath11k: QCA6390: prevents deep PC states before connecting to a network
Product:	Drivers	Reporter:	Mark Herbert (mark.herbert42)
Component:	network-wireless	Assignee:	drivers_network-wireless (drivers_network-wireless)
Status:	NEW ---
Severity:	normal	CC:	kvalo
Priority:	P3
Hardware:	All
OS:	Linux
Kernel Version:	5.17-next	Subsystem:
Regression:	No	Bisected commit-id:

Description Mark Herbert 2022-03-30 09:35:07 UTC

I remember there was a bug preventing CPU entering to deep powersaving
states so only PC3 was reached. (214543)

The bug itself is fixed - but I have just noticed a small remaining
issue. When I start my PC and there is no WIFI that I can connect so
ath11  is enabled but not connected to any network - it   prevents
entering into deep PC states again. PC3 is the deepest posible. When I connect to the WiFi network -deep PC states become reachable again.
 And when I disconnect after first connection  and keep my ath11k disconnected (exactly same situation as immediately after boot)- there is no issue.

So seems that this powersaving feature is not activated on boot but
only activates when the card connects to access point.  I am not good
enough in driver development and design a fix myself. So just writing
here

Comment 1 Mark Herbert 2022-05-17 16:41:00 UTC

Tried patches provided in ath11 mailing list, also tried to follow same logic and added psmode acivation to different places of driver init. I got a lot of messgesin ath11 debug mode (dmesg|grep ath11k|grep psmode)

[    6.802776] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[    6.824227] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[    6.833541] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[    7.180383] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[    7.187295] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[    7.204108] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[   10.036467] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[   10.049586] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[   10.051890] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[   10.303439] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[   10.314828] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  169.005363] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  169.012649] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  169.019348] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  171.961008] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  171.963190] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  171.976108] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  172.175797] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  172.244468] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  177.307027] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  177.365209] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  185.178483] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  185.179410] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  185.191395] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  185.353476] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  185.363617] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  238.575551] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  238.583375] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  238.693286] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  238.702605] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  287.829184] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  287.836666] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  287.895648] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  287.987780] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  288.655154] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  288.656374] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable
[  291.940117] ath11k_pci 0000:72:00.0: mac vdev 0 psmode enable

So the code to enable psmode does trigger, but it gives no difference till we have first connect to the network.

Comment 2 Kalle Valo 2023-03-17 05:43:54 UTC

Is this still happening?

I guess this was with QCA6390? Adding that to the title.