From: Kalle Valo <kvalo@kernel.org>
To: Mark Herbert <mark.herbert42@gmail.com>
Cc: ath11k@lists.infradead.org
Subject: Re: QCA6390 power saving issue
Date: Wed, 30 Mar 2022 11:00:51 +0300 [thread overview]
Message-ID: <87pmm3x424.fsf@kernel.org> (raw)
In-Reply-To: <a70aba8a-cce4-a84b-ea70-5761bde1cbe5@gmail.com> (Mark Herbert's message of "Tue, 29 Mar 2022 11:11:42 +0300")
Mark Herbert <mark.herbert42@gmail.com> writes:
> I remember there was a bug preventing CPU entering to deep powersaving
> states so only PC3 was reached.
>
> The but 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. 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
Seems very plausible to me. Can you file this to bugzilla, please?
Easier to track that way:
https://wireless.wiki.kernel.org/en/users/drivers/ath11k/bugreport
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2022-03-30 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 8:11 QCA6390 power saving issue Mark Herbert
2022-03-30 8:00 ` Kalle Valo [this message]
[not found] ` <da91be76-d609-ba29-76e6-5365ea1db9d4@gmail.com>
2022-03-30 12:47 ` Kalle Valo
2022-05-17 16:47 ` Mark Herbert
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=87pmm3x424.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=mark.herbert42@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.