All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Gross <andy.gross@linaro.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-pm@vger.kernel.org,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: Re: [PATCH v3] PM / sleep: enable suspend-to-idle even without registered suspend_ops
Date: Wed, 24 Aug 2016 00:18:06 -0500	[thread overview]
Message-ID: <CAPBZ5Qco3Y8an66851KJ3HUr9agk6yv7nNrhWA17hHGvbKWXTg@mail.gmail.com> (raw)
In-Reply-To: <1471614060-15120-1-git-send-email-sudeep.holla@arm.com>

On 19 August 2016 at 08:41, Sudeep Holla <sudeep.holla@arm.com> wrote:
> Suspend-to-idle (aka the "freeze" sleep state) is a system sleep state
> in which all of the processors enter deepest possible idle state and
> wait for interrupts right after suspending all the devices.
>
> There is no hard requirement for a platform to support and register
> platform specific suspend_ops to enter suspend-to-idle/freeze state.
> Only deeper system sleep states like PM_SUSPEND_STANDBY and
> PM_SUSPEND_MEM rely on such low level support/implementation.
>
> suspend-to-idle can be entered as along as all the devices can be
> suspended. This patch enables the support for suspend-to-idle even on
> systems that don't have any low level support for deeper system sleep
> states and/or don't register any platform specific suspend_ops.
>
> Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>

I tested this patch on the Qualcomm 410c platform.  It worked like a
charm.  Thanks for working on this!

Tested-by: Andy Gross <andy.gross@linaro.org>

  reply	other threads:[~2016-08-24  5:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18  9:19 [PATCH] PM / sleep: enable suspend-to-idle even without registered suspend_ops Sudeep Holla
2016-08-18 11:06 ` Rafael J. Wysocki
2016-08-18 13:10   ` Sudeep Holla
2016-08-18 16:42 ` [PATCH v2] " Sudeep Holla
2016-08-18 22:20   ` Rafael J. Wysocki
2016-08-19 13:41   ` [PATCH v3] " Sudeep Holla
2016-08-24  5:18     ` Andy Gross [this message]
2016-09-14  1:06     ` 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=CAPBZ5Qco3Y8an66851KJ3HUr9agk6yv7nNrhWA17hHGvbKWXTg@mail.gmail.com \
    --to=andy.gross@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=rjw@rjwysocki.net \
    --cc=sudeep.holla@arm.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.