mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Chen Yu <yu.c.chen@intel.com>
Cc: linux-acpi@vger.kernel.org,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Matt Fleming <matt@codeblueprint.co.uk>,
	Len Brown <lenb@kernel.org>, Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH][v6] ACPI / PM: Introduce efi poweroff for HW-full platforms without _S5
Date: Thu, 21 Apr 2016 02:17:27 +0200	[thread overview]
Message-ID: <1562468.HF88ABVP4x@vostro.rjw.lan> (raw)
In-Reply-To: <1458607870-22522-1-git-send-email-yu.c.chen@intel.com>

On Tuesday, March 22, 2016 08:51:10 AM Chen Yu wrote:
> The problem is Linux registers pm_power_off = efi_power_off only if
> we are in hardware reduced mode. Actually, what we also want is to do
> this when ACPI S5 is simply not supported on non-legacy platforms.
> Since some future Intel platforms are HW-full mode where the DSDT
> fails to supply an _S5 object(without SLP_TYP), we should let such
> kind of platform to leverage efi runtime service to poweroff.
> 
> This patch uses efi power off as first choice when S5 is unavailable,
> even if there is a customized poweroff(driver provided, eg).
> Meanwhile, the legacy platforms will not be affected because there is
> no path for them to overwrite the pm_power_off to efi power off.
> 
> Suggested-by: Len Brown <len.brown@intel.com>
> Reviewed-by: Matt Fleming <matt@codeblueprint.co.uk>
> Signed-off-by: Chen Yu <yu.c.chen@intel.com>

Applied, thanks!

      reply	other threads:[~2016-04-21  0:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-22  0:51 Chen Yu
2016-04-21  0:17 ` Rafael J. Wysocki [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=1562468.HF88ABVP4x@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=hpa@zytor.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=mingo@redhat.com \
    --cc=rafael@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=yu.c.chen@intel.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

all inboxes | Powered by JetHome®