All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 25 Feb 2021 09:21:48 +0100	[thread overview]
Message-ID: <20210225082148.GB6104@calypso> (raw)
In-Reply-To: <ca0dc6e4-364e-2525-b7d6-d02c2dc0c5fd@justinmp.com>

Hi Justin,

On Wed, Feb 24, 2021 at 05:38:12PM -0500, Justin Mazzola Paluska wrote:

> No, the behavior I see on a pre-2.0.0 BIOS is:
> 
> s2idle suspend works well (including getting into S0ix states) with no
> effort on my part.  I have no idea if s2idle does rfkill by itself, but all
> I do is shut the lid and the right thing happens.
> 
> Opportunistic S0ix (when the laptop is fully powered up and in use) only
> happens if I use rfkill to shut down WiFi and Bluetooth.  If either WiFi or
> Bluetooth are on, the laptop stays in power states well above the
> lowest-power SOix states.

Thanks for the clarification !

> It sounds like the 2.0.0 BIOS prevents whatever s2idle is doing from working
> without an rfkill.

Nope, rfkill or not, the 2.0.0 BIOS prevents s2idle (and opportunistic S0ix)
reach low power S0ix states. s2idle still kinda works (kernel says it enters
and exists s2idle suspend), but system remains in PC3 state instead of going
to PC10 and beyond.!

Stelian.
-- 
Stelian Pop <stelian@popies.net>

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

  reply	other threads:[~2021-02-25  8:22 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
2021-02-24 22:38                   ` Justin Mazzola Paluska
2021-02-25  8:21                     ` Stelian Pop [this message]
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=20210225082148.GB6104@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 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.