From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Daniel Wagner <daniel.wagner@bmw-carit.de>
Cc: linux-kernel@vger.kernel.org, Len Brown <len.brown@intel.com>,
Pavel Machek <pavel@ucw.cz>,
linux-pm@vger.kernel.org
Subject: Re: [RFC v0 2/9] suspend: Add getter function to report if freezing is active
Date: Sat, 05 Sep 2015 04:11:16 +0200 [thread overview]
Message-ID: <1683655.HLd9k04Slu@vostro.rjw.lan> (raw)
In-Reply-To: <1441373702-31796-3-git-send-email-daniel.wagner@bmw-carit.de>
On Friday, September 04, 2015 03:34:55 PM Daniel Wagner wrote:
> Instead encode the FREEZE state via the CPU state we allow the
> interesting subsystems (MCE, microcode) to query the power
> subsystem directly.
A use case, please.
> Most notifiers are not interested at all
> in this information so rather have explicit calls to freeze_active()
> instead adding complexity to the rest of the users of the CPU
> notifiers.
Why does it has anything to do with CPU notifiers? We don't offline
CPUs for suspend-to-idle.
> Signed-off-by: Daniel Wagner <daniel.wagner@bmw-carit.de>
> Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
> Cc: Len Brown <len.brown@intel.com>
> Cc: Pavel Machek <pavel@ucw.cz>
> Cc: linux-pm@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> ---
> include/linux/suspend.h | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/include/linux/suspend.h b/include/linux/suspend.h
> index 5efe743..5e15ade 100644
> --- a/include/linux/suspend.h
> +++ b/include/linux/suspend.h
> @@ -216,6 +216,11 @@ static inline bool idle_should_freeze(void)
> return unlikely(suspend_freeze_state == FREEZE_STATE_ENTER);
> }
>
> +static inline bool freeze_active(void)
> +{
> + return unlikely(suspend_freeze_state != FREEZE_STATE_NONE);
> +}
> +
> extern void freeze_set_ops(const struct platform_freeze_ops *ops);
> extern void freeze_wake(void);
>
> @@ -244,6 +249,7 @@ extern int pm_suspend(suspend_state_t state);
> static inline void suspend_set_ops(const struct platform_suspend_ops *ops) {}
> static inline int pm_suspend(suspend_state_t state) { return -ENOSYS; }
> static inline bool idle_should_freeze(void) { return false; }
> +static inline bool freeze_active(void) { return false; }
> static inline void freeze_set_ops(const struct platform_freeze_ops *ops) {}
> static inline void freeze_wake(void) {}
> #endif /* !CONFIG_SUSPEND */
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2015-09-05 1:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1441373702-31796-1-git-send-email-daniel.wagner@bmw-carit.de>
2015-09-04 13:34 ` [RFC v0 2/9] suspend: Add getter function to report if freezing is active Daniel Wagner
2015-09-05 2:11 ` Rafael J. Wysocki [this message]
2015-09-07 8:55 ` Daniel Wagner
2015-09-07 13:42 ` Rafael J. Wysocki
2015-09-07 21:44 ` Rafael J. Wysocki
2015-09-08 8:19 ` Daniel Wagner
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=1683655.HLd9k04Slu@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=daniel.wagner@bmw-carit.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
/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