From: Stewart Smith <stewart@linux•vnet.ibm.com>
To: Vasant Hegde <hegdevasant@linux•vnet.ibm.com>,
linuxppc-dev@lists•ozlabs.org, linux-leds@vger•kernel.org
Cc: cooloney@gmail•com, rpurdie@rpsys•net, khandual@linux•vnet.ibm.com
Subject: Re: [PATCH 1/2] powerpc/powernv: Add OPAL interfaces for accessing and modifying system LED states
Date: Thu, 19 Mar 2015 14:35:11 -0700 [thread overview]
Message-ID: <m37fucpt68.fsf@oc8180480414.ibm.com> (raw)
In-Reply-To: <20150308111408.3759.70606.stgit@localhost.localdomain>
Vasant Hegde <hegdevasant@linux•vnet.ibm.com> writes:
> From: Anshuman Khandual <khandual@linux•vnet.ibm.com>
>
> This patch registers the following two new OPAL interfaces calls
> for the platform LED subsystem. With the help of these new OPAL calls,
> the kernel will be able to get or set the state of various individual
> LEDs on the system at any given location code which is passed through
> the LED specific device tree nodes.
>
> (1) OPAL_LEDS_GET_INDICATOR opal_leds_get_ind
> (2) OPAL_LEDS_SET_INDICATOR opal_leds_set_ind
>
> Signed-off-by: Anshuman Khandual <khandual@linux•vnet.ibm.com>
> Signed-off-by: Vasant Hegde <hegdevasant@linux•vnet.ibm.com>
I also just merged the skiboot side of these calls.
Acked-by: Stewart Smith <stewart@linux•vnet.ibm.com>
Tested-by: Stewart Smith <stewart@linux•vnet.ibm.com>
(well, it boots, interacts with firmware. I didn't go and look at the
LEDs themselves).
next prev parent reply other threads:[~2015-03-19 21:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 11:13 [PATCH 0/2] LED interface for PowerNV platform Vasant Hegde
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 [this message]
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=m37fucpt68.fsf@oc8180480414.ibm.com \
--to=stewart@linux$(echo .)vnet.ibm.com \
--cc=cooloney@gmail$(echo .)com \
--cc=hegdevasant@linux$(echo .)vnet.ibm.com \
--cc=khandual@linux$(echo .)vnet.ibm.com \
--cc=linux-leds@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=rpurdie@rpsys$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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