public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nico.schottelius@ungleich.ch>
To: Mario.Limonciello@dell.com
Cc: linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org,
	andriy.shevchenko@linux.intel.com, dvhart@infradead.org,
	linux-kernel@vger.kernel.org,
	srinivas.pandruvada@linux.intel.com,
	mika.westerberg@linux.intel.com, tom@oneshoeco.com,
	jerome.debretagne@gmail.com, torvalds@linux-foundation.org,
	lv.zheng@intel.com
Subject: Re: Modern Suspend on Dell Latitude 5285 does not resume
Date: Fri, 21 Jul 2017 00:41:36 +0200	[thread overview]
Message-ID: <87r2xaloin.fsf@ungleich.ch> (raw)
In-Reply-To: <b967fdf2361d4ea29b8c76c62de0b7fc@ausx13mpc120.AMER.DELL.COM>


Good evening Mario,

> Currently the patch does not look at anything in the system to default to S2I vs S3.
> This will affect systems that offer S3 and S2I (even if S3 is broken).
>
> Have you configured /sys/power/mem_sleep to s2idle?
> https://github.com/torvalds/linux/blob/master/Documentation/power/states.txt#L35

indeed, after configuring it to s2idle, it works like charm!

Do you have any plans on defaulting to s2idle for machines that do not
properly support s3?

Best,

Nico


--
Modern, affordable, Swiss Virtual Machines can be found on www.datacenterlight.ch

  reply	other threads:[~2017-07-20 22:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20 18:24 Modern Suspend on Dell Latitude 5285 does not resume Nico Schottelius
2017-07-20 21:03 ` Mario.Limonciello
2017-07-20 22:41   ` Nico Schottelius [this message]
2017-07-20 23:05     ` Rafael J. Wysocki
2017-07-20 21:03 ` Rafael J. Wysocki

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=87r2xaloin.fsf@ungleich.ch \
    --to=nico.schottelius@ungleich.ch \
    --cc=Mario.Limonciello@dell.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dvhart@infradead.org \
    --cc=jerome.debretagne@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lv.zheng@intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=tom@oneshoeco.com \
    --cc=torvalds@linux-foundation.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