From: Vipin K Parashar <vipin@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: mpe@ellerman.id.au, joel@jms.id.au, stewart@linux.vnet.ibm.com,
vaibhav@linux.vnet.ibm.com,
Vipin K Parashar <vipin@linux.vnet.ibm.com>
Subject: [RESEND PATCH v8] powerpc/powernv: Add poweroff (EPOW, DPO) events support for PowerNV platform
Date: Thu, 11 Jun 2015 17:13:12 +0530 [thread overview]
Message-ID: <1434022993-20028-1-git-send-email-vipin@linux.vnet.ibm.com> (raw)
This patch adds support for OPAL EPOW (Early Power Off Warning) 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.
Reviewed-by: Joel Stanley <joel@jms.id.au>
Reviewed-by: Vaibhav Jain <vaibhav@linux.vnet.ibm.com>
Reviewed-by: Michael Ellerman <mpe@ellerman.id.au>
Changes in v8:
- Added logic to filter events which doesn't require system shutdown
for EPOW scenario.
- Re-phrased patch description.
Changes in v7:
- Fixed logic to check epow support to avoid EPOW, DPO handling path
for BMC systems.
Changes in v6:
- Made below changes as suggested by Michael Ellerman on previous patch.
- Changed EPOW, DPO notifier blocks to use opal_power_control_event()
and enhanced opal_power_control_event() to handle EPOW and DPO events.
- Reorganized code and added/changed few variable, function names removing
older ones.
- Minor cleanup like removing unused headers, blank lines etc.
Changes in v5:
- Made changes to address review comments on previous patch.
Changes in v4:
- Made changes to address review comments on previous patch.
Changes in v3:
- Made changes to immediately call orderly_poweroff upon receipt of
OPAL EPOW, DPO notifications.
- Made code changes to address review comments on previous patch.
- Made code changes to use existing OPAL EPOW API.
- Removed patch to extract EPOW event timeout from OPAL device-tree.
Changes in v2:
- Made code changes to improve code as per previous review comments.
- Added patch to obtain EPOW event timeout values from OPAL device-tree.
Vipin K Parashar (1):
powerpc/powernv: Add poweroff (EPOW, DPO) events support for PowerNV
platform
arch/powerpc/include/asm/opal-api.h | 40 +++++++
arch/powerpc/include/asm/opal.h | 3 +-
arch/powerpc/platforms/powernv/opal-power.c | 147 ++++++++++++++++++++++---
arch/powerpc/platforms/powernv/opal-wrappers.S | 1 +
4 files changed, 173 insertions(+), 18 deletions(-)
--
1.9.3
next reply other threads:[~2015-06-11 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 11:43 Vipin K Parashar [this message]
2015-06-11 11:43 ` [RESEND PATCH v8] powerpc/powernv: Add poweroff (EPOW, DPO) events support for PowerNV platform Vipin K Parashar
2015-06-26 16:30 ` Vipin K Parashar
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=1434022993-20028-1-git-send-email-vipin@linux.vnet.ibm.com \
--to=vipin@linux.vnet.ibm.com \
--cc=joel@jms.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=stewart@linux.vnet.ibm.com \
--cc=vaibhav@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).