linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Vipin K Parashar <vipin@linux.vnet.ibm.com>,
	linuxppc-dev@lists.ozlabs.org
Cc: stewart@linux.vnet.ibm.com,
	Vipin K Parashar <vipin@linux.vnet.ibm.com>,
	joel@jms.id.au, vaibhav@linux.vnet.ibm.com
Subject: Re: [v9] powerpc/powernv: Add poweroff (EPOW, DPO) events support for PowerNV platform
Date: Thu, 16 Jul 2015 19:54:57 +1000 (AEST)	[thread overview]
Message-ID: <20150716095458.0A1B5140778@ozlabs.org> (raw)
In-Reply-To: <1436353561-19466-2-git-send-email-vipin@linux.vnet.ibm.com>

On Wed, 2015-08-07 at 11:06:01 UTC, Vipin K Parashar wrote:
> This patch adds support for OPAL EPOW (Environmental and Power Warnings)
> and DPO (Delayed Power Off) events for the PowerNV platform. These events
> are generated on FSP (Flexible Service Processor) based systems. EPOW
> events are generated due to various critical system conditions that
> require system shutdown. A few examples of these conditions are high
> ambient temperature or system running on UPS power with low UPS battery.
> DPO event is generated in response to admin initiated system shutdown
> request. Upon receipt of EPOW and DPO events the host kernel invokes
> orderly_poweroff() for performing graceful system shutdown.
> 
> Signed-off-by: Vipin K Parashar <vipin@linux.vnet.ibm.com>
> Acked-by: Vaibhav Jain <vaibhav@linux.vnet.ibm.com>

Applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/3b476aadbc1409fef6be

cheers

      reply	other threads:[~2015-07-16  9:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 11:06 [PATCH v9] powerpc/powernv: Add poweroff (EPOW, DPO) events support for PowerNV platform Vipin K Parashar
2015-07-08 11:06 ` Vipin K Parashar
2015-07-16  9:54   ` Michael Ellerman [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=20150716095458.0A1B5140778@ozlabs.org \
    --to=mpe@ellerman.id.au \
    --cc=joel@jms.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=stewart@linux.vnet.ibm.com \
    --cc=vaibhav@linux.vnet.ibm.com \
    --cc=vipin@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).