public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Tom Cook <tom.k.cook@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Power management - HP 15-ds0502na
Date: Mon, 4 Nov 2019 10:45:23 -0500	[thread overview]
Message-ID: <20191104154523.GH28764@mit.edu> (raw)
In-Reply-To: <20191104150648.GG28764@mit.edu>

On Mon, Nov 04, 2019 at 10:06:48AM -0500, Theodore Y. Ts'o wrote:
> Actually, it's probably because one of the device drives isn't
> properly putting that particular device into a low power state.  When
> I was trying to make s2idle work on the XPS 13, there was needed patch
> to make the SATA AHCI controller go into a lower power state.  This
> was a patch which the Dell folks had gotten into their special
> "Optimized for Dell laptops" Ubuntu kernel that was running into
> resistance upstream.  I *think* that patch finally made it upstream,
> but to be honest, I haven't been keeping track since I decided "life
> was too short to fight and make s2idle work".

Oh, and I forgot; the other thing I had to do to get s2idle's power
consumption down to suspend-2-ram was to unload the SD card reader;
apparently that device driver didn't know how to do the low power
saving thing under OS control.  So I ultimately was able to get the
power while suspended of s2idle down to that of s2ram.  What I wasn't
able to solve for my laptop was the reliability of resuming after the
suspend....

						- Ted

      reply	other threads:[~2019-11-04 15:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 11:21 Power management - HP 15-ds0502na Tom Cook
2019-11-04 13:51 ` Theodore Y. Ts'o
2019-11-04 14:32   ` Tom Cook
2019-11-04 15:06     ` Theodore Y. Ts'o
2019-11-04 15:45       ` Theodore Y. Ts'o [this message]

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=20191104154523.GH28764@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tom.k.cook@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox