linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vipin K Parashar <vipin@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Vipin K Parashar <vipin@linux.vnet.ibm.com>
Subject: [PATCH 0/2] OPAL Poweroff events driver for PowerNV platform
Date: Fri, 10 Apr 2015 12:22:11 +0530	[thread overview]
Message-ID: <1428648733-23826-1-git-send-email-vipin@linux.vnet.ibm.com> (raw)

OPAL Poweroff events driver handles poweroff events on PowerNV platform.
Currently this driver supports EPOW (Early Power Off Warning) and
Delayed Power Off (DPO) events on FSP based systems.
	EPOW events are generated by SPCN/FSP due to various critical system
conditions that need system shutdown. Few examples of these conditions are
high ambient temperature or system running on UPS power with UPS battery low.
DPO event is generated in reponse to user initiated system shutdown request.
	OPAL Poweroff events driver handles OPAL notifications for these events,
processes them, starts kernel system poweroff timers and send uevents to notify
udev. Poweroff event attributes are exposed as attributes files for platform
device opal-poweroff-events. Host userspace should add udev scripts to perform
various actions like sending event info to guests for graceful guest shutdown
and host poweroff scripts.

Below attribute files are created for platform device opal-poweroff-events:

admin_shutdown - Poweroff needed due to admin requested shutdown
        Values as below:
        No
        Yes

power_supply - Poweroff needed due to UPS/internal battery
        Values as below:
        Normal
        UPS
        UPS-low

thermal - Poweroff needed due to high, critical ambient or internal temp
        Values as below:
        Normal
        High-ambient-temp
        Critical-ambient-temp
        High-internal-temp
        Critical-internal-temp

timeout: Time allowed for poweroff

Vipin K Parashar (2):
  powerpc/powernv: OPAL poweroff events driver for PowerNV platform
  powerpc/powernv: Add udev notification and poweroff event attributes

 arch/powerpc/include/asm/opal.h                    |  22 +
 arch/powerpc/platforms/powernv/Makefile            |   2 +-
 .../platforms/powernv/opal-poweroff-events.c       | 567 +++++++++++++++++++++
 .../platforms/powernv/opal-poweroff-events.h       |  35 ++
 arch/powerpc/platforms/powernv/opal-wrappers.S     |   3 +-
 arch/powerpc/platforms/powernv/opal.c              |   8 +-
 6 files changed, 634 insertions(+), 3 deletions(-)
 create mode 100644 arch/powerpc/platforms/powernv/opal-poweroff-events.c
 create mode 100644 arch/powerpc/platforms/powernv/opal-poweroff-events.h

--
1.9.3

             reply	other threads:[~2015-04-10  6:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10  6:52 Vipin K Parashar [this message]
2015-04-10  6:52 ` [PATCH 1/2] powerpc/powernv: OPAL Poweroff events driver for PowerNV platform Vipin K Parashar
2015-04-10  6:52 ` [PATCH 2/2] powerpc/powernv: Add udev notification and poweroff event attributes 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=1428648733-23826-1-git-send-email-vipin@linux.vnet.ibm.com \
    --to=vipin@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).