linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, linux-leds@vger.kernel.org
Cc: cooloney@gmail.com, rpurdie@rpsys.net, khandual@linux.vnet.ibm.com
Subject: [PATCH 0/2] LED interface for PowerNV platform
Date: Sun, 08 Mar 2015 16:43:57 +0530	[thread overview]
Message-ID: <20150308110558.3759.72635.stgit@localhost.localdomain> (raw)

The following series implements LED driver for PowerNV platform.

PowerNV platform has below type of indicators:
  - System attention indicator (Check log indicator)
        Indicates there is a problem with the system that needs attention.
  - Identify
        Helps the user locate/identify a particular FRU or resource in the
        system.
  - Fault
	Indicates there is a problem with the FRU or resource at the
	location with which the indicator is associated.

On PowerNV (Non Virtualized) platform OPAL firmware provides LED
information to host via device tree (location code and LED type).
During init we check for 'ibm,opal/led' node in device tree to
enabled LED driver. And we use OPAL API's to get/set LEDs.

patch 1/2: PowerNV architecture specific code. This adds necessary
  OPAL APIs.
patch 2/2 is actual LED driver implemenation for PowerNV platform.

TODO:
  - Add support for System Attention Indicator
---
Anshuman Khandual (2):
      powerpc/powernv: Add OPAL interfaces for accessing and modifying system LED states
      leds/powernv: Add driver for PowerNV platform


 arch/powerpc/include/asm/opal.h                |   19 +
 arch/powerpc/platforms/powernv/opal-wrappers.S |    2 
 arch/powerpc/platforms/powernv/opal.c          |   12 
 drivers/leds/Kconfig                           |    9 
 drivers/leds/Makefile                          |    1 
 drivers/leds/leds-powernv.c                    |  599 ++++++++++++++++++++++++
 6 files changed, 635 insertions(+), 7 deletions(-)
 create mode 100644 drivers/leds/leds-powernv.c

--
Vasant
Signature

             reply	other threads:[~2015-03-08 11:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-08 11:13 Vasant Hegde [this message]
2015-03-08 11:14 ` [PATCH 1/2] powerpc/powernv: Add OPAL interfaces for accessing and modifying system LED states Vasant Hegde
2015-03-19 21:35   ` Stewart Smith
2015-03-20  6:23   ` Michael Ellerman
2015-03-20  8:07     ` Vasant Hegde
2015-03-08 11:14 ` [PATCH 2/2] leds/powernv: Add driver for PowerNV platform Vasant Hegde
2015-03-19 21:35   ` Stewart Smith

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=20150308110558.3759.72635.stgit@localhost.localdomain \
    --to=hegdevasant@linux.vnet.ibm.com \
    --cc=cooloney@gmail.com \
    --cc=khandual@linux.vnet.ibm.com \
    --cc=linux-leds@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=rpurdie@rpsys.net \
    /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).