From: Gavin Shan <shangw@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Gavin Shan <shangw@linux.vnet.ibm.com>
Subject: [PATCH 2/5] powernv/opal: Disable OPAL notifier upon poweroff
Date: Thu, 20 Jun 2013 18:13:23 +0800 [thread overview]
Message-ID: <1371723206-26190-3-git-send-email-shangw@linux.vnet.ibm.com> (raw)
In-Reply-To: <1371723206-26190-1-git-send-email-shangw@linux.vnet.ibm.com>
While we're restarting or powering off the system, we needn't
the OPAL notifier any more. So just to disable that.
Signed-off-by: Gavin Shan <shangw@linux.vnet.ibm.com>
---
arch/powerpc/platforms/powernv/setup.c | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/platforms/powernv/setup.c b/arch/powerpc/platforms/powernv/setup.c
index d4459bf..84438af 100644
--- a/arch/powerpc/platforms/powernv/setup.c
+++ b/arch/powerpc/platforms/powernv/setup.c
@@ -93,6 +93,8 @@ static void __noreturn pnv_restart(char *cmd)
{
long rc = OPAL_BUSY;
+ opal_notifier_disable();
+
while (rc == OPAL_BUSY || rc == OPAL_BUSY_EVENT) {
rc = opal_cec_reboot();
if (rc == OPAL_BUSY_EVENT)
@@ -108,6 +110,8 @@ static void __noreturn pnv_power_off(void)
{
long rc = OPAL_BUSY;
+ opal_notifier_disable();
+
while (rc == OPAL_BUSY || rc == OPAL_BUSY_EVENT) {
rc = opal_cec_power_down(0);
if (rc == OPAL_BUSY_EVENT)
--
1.7.5.4
next prev parent reply other threads:[~2013-06-20 10:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 10:13 [PATCH v7 0/5] EEH Support for PowerNV platform Gavin Shan
2013-06-20 10:13 ` [PATCH 1/5] powernv/opal: Notifier for OPAL events Gavin Shan
2013-06-20 10:13 ` Gavin Shan [this message]
2013-06-20 10:13 ` [PATCH 3/5] powerpc/eeh: Register OPAL notifier for PCI error Gavin Shan
2013-06-20 10:13 ` [PATCH 4/5] powerpc/powernv: Debugfs directory for PHB Gavin Shan
2013-06-20 10:13 ` [PATCH 5/5] powerpc/eeh: Debugfs for error injection Gavin Shan
2013-06-20 10:17 ` [PATCH v7 0/5] EEH Support for PowerNV platform Gavin Shan
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=1371723206-26190-3-git-send-email-shangw@linux.vnet.ibm.com \
--to=shangw@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).