From: Stelian Pop <stelian@popies.net>
To: Justin Mazzola Paluska <jmp@justinmp.com>
Cc: ath11k@lists.infradead.org, kvalo@codeaurora.org
Subject: Re: Ordering Dell XPS 13 9310 to test QCA6390
Date: Wed, 24 Feb 2021 23:02:46 +0100 [thread overview]
Message-ID: <20210224220246.GA6104@calypso> (raw)
In-Reply-To: <bbec5e34-49e4-1e80-0420-63cb046a2c2b@justinmp.com>
[Sorry for the previous HTML mail...]
Hi Justin,
On Wed, Feb 24, 2021 at 04:33:03PM -0500, Justin Mazzola Paluska wrote:
> On 2/24/21 4:14 AM, Stelian Pop wrote:
> > There are probably multiple issues, the first of which is the one Justin
> > reported (unable to go to sleep when ath11k is loaded). I suggest you
> > look into this BEFORE updating the BIOS...
>
> To be clear, s2idle works (and I do get into S0ix states when doing s2idle
> suspend) for me with the pre-2.0.0 BIOS.
As you said previously, entering S0ix only works if you 'rfkill block all'
first before going into s2idle suspend. That was the issue I was referring
to.
Stelian.
--
Stelian Pop <stelian@popies.net>
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2021-02-24 22:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 14:41 Ordering Dell XPS 13 9310 to test QCA6390 Mitchell Nordine
2020-12-16 15:46 ` Kalle Valo
2021-01-13 10:25 ` Kalle Valo
2021-01-13 10:40 ` wi nk
2021-01-13 11:54 ` Kalle Valo
2021-01-13 12:02 ` wi nk
2021-01-13 15:22 ` [**EXTERNAL**] " Luo, Sining
2021-01-13 17:05 ` Kalle Valo
2021-01-13 18:29 ` Luo, Sining
2021-01-16 14:10 ` Justin Mazzola Paluska
2021-02-12 7:14 ` Kalle Valo
2021-02-13 19:10 ` Justin Mazzola Paluska
2021-02-22 16:10 ` Kalle Valo
2021-02-24 9:14 ` Stelian Pop
2021-02-24 21:33 ` Justin Mazzola Paluska
2021-02-24 22:02 ` Stelian Pop [this message]
2021-02-24 22:38 ` Justin Mazzola Paluska
2021-02-25 8:21 ` Stelian Pop
2021-03-06 20:22 ` Wren Turkal
2021-03-06 20:49 ` Stelian Pop
2021-03-07 4:48 ` Wren Turkal
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=20210224220246.GA6104@calypso \
--to=stelian@popies.net \
--cc=ath11k@lists.infradead.org \
--cc=jmp@justinmp.com \
--cc=kvalo@codeaurora.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