Define Generic LED groups for all the platforms

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: Iaa081e59a356670b9f713db11bd45dbda55a6bd4
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>

1 files changed, 0 insertions, 11 deletions

diff --git a/meta-openbmc-machines/meta-openpower/meta-rackspace/meta-barreleye/recipes-phosphor/leds/phosphor-led-manager%.bbappend b/meta-openbmc-machines/meta-openpower/meta-rackspace/meta-barreleye/recipes-phosphor/leds/phosphor-led-manager%.bbappend
deleted file mode 100644
index dbbbc8811..000000000
--- a/meta-openbmc-machines/meta-openpower/meta-rackspace/meta-barreleye/recipes-phosphor/leds/phosphor-led-manager%.bbappend
+++ /dev/null
@@ -1,11 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-SYSTEMD_LINK_${PN} += "../obmc-led-group-start@.service:${SYSTEMD_DEFAULT_TARGET}.wants/obmc-led-group-start@BmcBooted.service"
-
-STATES = "start stop"
-TMPLFMT = "obmc-led-group-{0}@.service"
-TGTFMT = "obmc-power-{0}@0.target"
-INSTFMT = "obmc-led-group-{0}@PowerOn.service"
-FMT = "../${TMPLFMT}:${TGTFMT}.wants/${INSTFMT}"
-
-SYSTEMD_LINK_${PN} += "${@compose_list(d, 'FMT', 'STATES')}"