summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVishwanatha Subbanna <vishwa@linux.vnet.ibm.com>2017-03-29 21:35:12 +0530
committerVishwanatha Subbanna <vishwa@linux.vnet.ibm.com>2017-03-29 21:35:12 +0530
commit169ff8aa8801b2cc4b1582505c6f14bc268c0a11 (patch)
tree1d2cfc8cd89c5db71bb448d7928f38b17f0aa875
parent32bb6f895c993e174799597de368bd9300aa62b3 (diff)
downloadphosphor-led-manager-169ff8aa8801b2cc4b1582505c6f14bc268c0a11.tar.gz
phosphor-led-manager-169ff8aa8801b2cc4b1582505c6f14bc268c0a11.zip
LEDS: Add default LED groups
Regardless of the machine type, there needs to be standard set of LED groups that would get asserted / de-asserted under these conditions: 1) BMC booted 2) Power On 3) Power Off This makes sense on hardwares that have physical LEDs. However, QEMU does not have physical LEDs associated with the groups but the groups themselves can be in asserted state so that if physical LEDs are implemented in future, they can be used. Change-Id: Ie66f5ac59fcdbecb7ba79c4dbcbdc8fceaace42f Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
-rwxr-xr-xled.yaml10
1 files changed, 10 insertions, 0 deletions
diff --git a/led.yaml b/led.yaml
index e36762b..d1eb692 100755
--- a/led.yaml
+++ b/led.yaml
@@ -1,3 +1,13 @@
+bmc_booted:
+ heartbeat:
+ Action: 'On'
+ DutyOn: 50
+ Period: 0
+power_on:
+ power:
+ Action: 'On'
+ DutyOn: 50
+ Period: 0
enclosure_fault:
fault_front:
Action: 'On'
OpenPOWER on IntegriCloud