From: Mark Herbert <mark.herbert42@gmail.com>
To: ath11k@lists.infradead.org
Subject: Re: High battery usage with ath11k on Dell 9310
Date: Wed, 13 Oct 2021 19:37:48 +0300 [thread overview]
Message-ID: <e5da99ce-a8a0-24b9-9e05-5f575456fb94@gmail.com> (raw)
In-Reply-To: <c2c790a6-b86a-6664-e147-bc642e00e325@gmail.com>
I've tried to apply
[PATCH] ath11k: enable power save in station mode
It did not apply over the ath-next but being applied manually drivers
compiled and I can now reach PC8 state. And it stays pretty much time
there -88% if laptop is idle. So I hope if this patch will make it to
the main tree it will solve one of the bugs.
On 10.10.2021 15:24, Mark Herbert wrote:
> Simply disabling wifi drops 0.8-1 watts from power consumption.
> Comparing almost same model (16 gb RAM vs 32) but based on Intel card
> shows the same difference - Intel based laptop with WiFi connected
> consumes about same as ath11k with Wifi discnnected.
>
> Powertop newer shows PC states below PC6. Disabling WiFi allows PC8,
> disabling ath11k completely (bios) - PC10.
>
> Wifi enabled
>
> Pkg(HW)
> C2 (pc2) 18,5% |
> C3 (pc3) 14,2% |
> C6 (pc6) 47,5% |
> C7 (pc7) 0,0% |
> C8 (pc8) 0,0% |
> C9 (pc9) 0,0% |
> C10 (pc10) 0,0% |
>
> Wfi disabled (by networkmanager/nm-applet)
>
>
> Pkg(HW)
> C2 (pc2) 10,8% |
> C3 (pc3) 18,5% |
> C6 (pc6) 1,1% |
> C7 (pc7) 0,3% |
> C8 (pc8) 28,3% |
> C9 (pc9) 0,0% |
> C10 (pc10) 0,0% |
>
> Seems that even on no network activity ath11k forces CPU to stay awake
> and eat battery. There are some background transfer happening as I
> have Viber, thunderbird and firefox opened so I bet they do sent some
> but there is no file transfers, media streams etc. Under the same
> conditions (taking this disk from one 9310 to other 9310 - same
> software, same kernel - just wifi's different) - iwlwifi manages to
> reach PC8-PC10 being connected. With ath10k on dell XPS-13 9350 intel
> also was saving battery much better than ath10k, bit there was like
> 88% of PC10 with intel and 65% PC10 and 20% PC8 with ath10k. But it
> was not such terribly bad as with ath11.
>
> There is already kernel bug for this, not creating duplicates
>
> https://bugzilla.kernel.org/show_bug.cgi?id=214543
>
>
>
>
>
>
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2021-10-13 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 12:24 High battery usage with ath11k on Dell 9310 Mark Herbert
2021-10-11 5:41 ` Kalle Valo
2021-10-13 16:37 ` Mark Herbert [this message]
2021-10-20 8:16 ` Kalle Valo
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=e5da99ce-a8a0-24b9-9e05-5f575456fb94@gmail.com \
--to=mark.herbert42@gmail.com \
--cc=ath11k@lists.infradead.org \
/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