summaryrefslogtreecommitdiffstats
path: root/doc/device-tree
diff options
context:
space:
mode:
authorVasant Hegde <hegdevasant@linux.vnet.ibm.com>2015-04-06 14:01:34 +0530
committerStewart Smith <stewart@linux.vnet.ibm.com>2015-05-07 17:42:34 +1000
commitb25e34639cc6410c9e0cdb08808415f548bc00bb (patch)
tree1e76410a54eaf45bfec6de1218a67792fc16fe59 /doc/device-tree
parent579892d785a903303eb3ebf7c7dd343752cd8286 (diff)
downloadtalos-skiboot-b25e34639cc6410c9e0cdb08808415f548bc00bb.tar.gz
talos-skiboot-b25e34639cc6410c9e0cdb08808415f548bc00bb.zip
hdata: Detect LED mode and populate device tree
FSP based machine supports two different LED modes: - Light Path : Both identify and fault LEDs are supported - Guiding Light: Only identify LEDs are supported And this information is passed to OPAL via HDAT. Lets parse this and populate the device tree. Later LED driver uses this information to populate indivisual LED node. Device Tree property: /ibm,opal/led/led-mode : lightpath/guidinglight Signed-off-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com> Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Diffstat (limited to 'doc/device-tree')
-rw-r--r--doc/device-tree/ibm,opal/led.txt3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/device-tree/ibm,opal/led.txt b/doc/device-tree/ibm,opal/led.txt
index faff1e85..2ce6946f 100644
--- a/doc/device-tree/ibm,opal/led.txt
+++ b/doc/device-tree/ibm,opal/led.txt
@@ -8,6 +8,7 @@ led {
compatible = "ibm,opal-v3-led";
phandle = <0x1000006b>;
linux,phandle = <0x1000006b>;
+ led-mode = "lightpath";
U78C9.001.RST0027-P1-C1 {
led-types = "identify", "fault";
@@ -21,6 +22,8 @@ led {
'compatible' property describes LEDs compatibility.
+'led-mode' property describes service indicator mode (lightpath/guidinglight).
+
Each node under 'led' node describes location code of FRU/Enclosure.
The properties under each node:
OpenPOWER on IntegriCloud