From: Mark Herbert <mark.herbert42@gmail.com>
To: Manikanta Pubbisetty <quic_mpubbise@quicinc.com>,
"Limonciello, Mario" <mario.limonciello@amd.com>,
ath11k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/4] ath11k: Enable low power mode when WLAN is not active
Date: Mon, 29 Aug 2022 09:27:19 +0300 [thread overview]
Message-ID: <b4b5a72e-4ad2-e249-c71c-c64cf5902a66@gmail.com> (raw)
In-Reply-To: <7df6efae-0797-a27a-1372-db7ad16e71d2@quicinc.com>
On 8/29/22 08:30, Manikanta Pubbisetty wrote:
> On 8/26/2022 2:31 AM, Mark Herbert wrote:
>>>
>>>> The changes that I have posted will not work on other targets like
>>>> WCN6855 as is. It requires additional changes and therefore lots of
>>>> testing.
>>>
>>
>> Will the changes be possible for QCA6390 as well? Currently this
>> chip only activates power saving mode when it is connected, but
>> behaves badly when not associated to any network. So there is a
>> chance that this kind of solution will help.
>>
>
> Not associated to any network as in Wi-Fi is ON and not connected or
> Wi-Fi is off?
>
> Manikanta
The way it works now.
I boot my laptop (it is Dell XPS 13 9310). If the network is available
and QCA6390 associates with it - the CPU package goes for PC10 state
for about 70% of time on idle. Even if I disconnect now it will be still
good.
But if I boot my laptop and never connect (associate to any WiFi ) - the
CPU will never reach below PC3 with WiFi on. If I disable WiFi - it
reaches PC10, if enable back - again PC3.
The point is QCA6390 need to be associated to network after boot (or
hibernation resume) before it activates powersave mode. If this very
first associatiion is not happening - it will eat battery as mad.
For now I've workarounded it by setting a systemd timer service to check
if the WiFi is not associated for f 3 minutes and if it is not - switch
wifi off.
But it is very strange why this first association is mandatory, because
if this forst association after boot happened - QCA6390 behaves
perfectly with WiFi on but not asociated. And continue to work perfectly
until hardware restart (reboot or hibernate resume) - then again first
association is needed. I was thinking that it is happening because the
ath11k_mac_vif_setup_ps is called only after the association so I've
tested the patch to call it earlier, and still no luck.
next prev parent reply other threads:[~2022-08-29 6:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 13:49 [PATCH 0/4] ath11k: Enable low power mode when WLAN is not active Manikanta Pubbisetty
2022-07-20 13:49 ` [PATCH 1/4] ath11k: Fix double free issue during SRNG deinit Manikanta Pubbisetty
2022-07-20 13:49 ` [PATCH 2/4] ath11k: Move hardware initialization logic to start() Manikanta Pubbisetty
2022-07-20 13:49 ` [PATCH 3/4] ath11k: Enable low power mode when WLAN is not active Manikanta Pubbisetty
2022-07-20 13:49 ` [PATCH 4/4] ath11k: Fix failed to parse regulatory event print Manikanta Pubbisetty
2022-07-22 22:00 ` [PATCH 0/4] ath11k: Enable low power mode when WLAN is not active Limonciello, Mario
2022-07-23 12:09 ` Limonciello, Mario
2022-08-25 11:24 ` Manikanta Pubbisetty
2022-08-25 17:16 ` Limonciello, Mario
2022-08-25 21:01 ` Mark Herbert
2022-08-29 5:30 ` Manikanta Pubbisetty
2022-08-29 6:27 ` Mark Herbert [this message]
2022-08-29 5:28 ` Manikanta Pubbisetty
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=b4b5a72e-4ad2-e249-c71c-c64cf5902a66@gmail.com \
--to=mark.herbert42@gmail.com \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=quic_mpubbise@quicinc.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox