| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
The phosphor-led-manager no longer assumes a default led priority
of 'Blink'.
Follow the LED priority configuration instruction [1], The LED priority
needs to be explicitly configured.
Also add the gpio_fault, psu_fault, ras_ue_fault led groups to
Mt.Jade's configuration.
[1] https://github.com/openbmc/phosphor-led-manager/blob/master/README.md#configuration-led-priority
Signed-off-by: Chanh Nguyen <chanh@os.amperecomputing.com>
Change-Id: I4206c8e49cc19bbc56d62afca357446edee874c4
|
|
Update LED names to follow LED name convention at
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/leds/leds-gpio.yaml
Also add more LED groups that applications might potential use.
Tested:
1. Check LED group in dbus to have expected groups
root@mtmitchell-dcscm:~# busctl tree xyz.openbmc_project.LED.GroupManager
`- /xyz
`- /xyz/openbmc_project
`- /xyz/openbmc_project/led
`- /xyz/openbmc_project/led/groups
|- /xyz/openbmc_project/led/groups/bmc_booted
|- /xyz/openbmc_project/led/groups/enclosure_identify
|- /xyz/openbmc_project/led/groups/enclosure_identify_blink
|- /xyz/openbmc_project/led/groups/fan0_fault
|- /xyz/openbmc_project/led/groups/fan1_fault
|- /xyz/openbmc_project/led/groups/fan2_fault
|- /xyz/openbmc_project/led/groups/fan3_fault
|- /xyz/openbmc_project/led/groups/fan4_fault
|- /xyz/openbmc_project/led/groups/fan5_fault
|- /xyz/openbmc_project/led/groups/gpio_fault
|- /xyz/openbmc_project/led/groups/overtemp_fault
|- /xyz/openbmc_project/led/groups/power_on
|- /xyz/openbmc_project/led/groups/psu_fault
|- /xyz/openbmc_project/led/groups/ras_ue_fault
`- /xyz/openbmc_project/led/groups/systemFault
2. Check journal log to ensure no error related to LED configuration.
Change-Id: I2ef1ba810a6b91dad7d87d9dffb06145ce023e9d
Signed-off-by: Chanh Nguyen <chanh@os.amperecomputing.com>
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
|
|
Currently just one LED group for FAN fault check. This causes FAN
fault LED might be changed to OFF even when still having failure on
some FANs.
This commit changes to have LED group for each FAN to fix this issue.
Tested:
1. Unplug two random FANs
2. Plug one FAN into the board and verify that FAN Led status is
still on
3. Plug all FAN into the board and verify that FAN Led status is off.
Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: I8cf2eeafbe7372b0eda85c133e88a228b5cd0a2a
|
|
phosphor-led-manager is changed to use xyz.openbmc_project.Inventory.
Decorator.Compatible interface to select the configuration file.
This updates the led-group-config.json file to
com.ampere.Hardware.Chassis.Model.MtMitchell.json follow the
phosphor-led-manager.
Tested: verify that led config file in the system
root@mtmitchell-dcscm:~# ls /usr/share/phosphor-led-manager/
com.ampere.Hardware.Chassis.Model.MtMitchell.json
com.ibm.Hardware.Chassis.Model.Rainier1S4U.json
com.ibm.Hardware.Chassis.Model.Rainier4U.json
com.ibm.Hardware.Chassis.Model.Everest.json
com.ibm.Hardware.Chassis.Model.Rainier2U.json
Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: Id7a2f885a933319b8b09279689dfb627c843cf88
|
|
This commit adds bmc_ready and sw_heartbeat leds to bmc_booted group.
When BMC's status is Ready, phosphor-led-manager shall assert bmc_ready
GPIO and create bmc/sw heart-beat signals to CPLD/HOST.
By the heartbeat signals are create by leds, the service to create
heartbeat signals is redundant, therefore ampere-bmc-heartbeat.service
shall be removed.
Tested:
1. Turn on/off, power cycle, reboot host features work correctly.
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>
Change-Id: If21649c1a70a6b43acf8130561181e534f762b61
|
|
Assert Fault LED when detecting OVERTEMP signal asserted.
This is done by adding new overtemp_fault LED group and
update the overtemp service to assert/de-assert the LED
group.
1. Start the ampere_overtemp@.service
2. Verify that the `Fault Led` is turned on and turn off after 10s.
3. Verify that Thermal Trip SEL is created.
Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: Ifbc203bf79a13741082d84850b9e75ca6148a6cd
|
|
The phosphor-led-manager will monitors the
`xyz.openbmc_project.State.Decorator.OperationalStatus` interface
of the Inventory D-Bus object, and check whether the Inventory
D-Bus object is associated with the LED group D-Bus object, and
then update the Asserted property of the LedManager.
This adds the fan_fault led group to associations.json file to
monitors the FANs and turns on the fault led when the FANs fails.
1. Unplug the fan and verify that both `Fan Fault Led` and
`Fault Led` are turned on.
2. Plug the fan and verify that both `Fan Fault Led` and `Fault Led`
are turned off.
Signed-off-by: Hieu Huynh <hieuh@os.amperecomputing.com>
Change-Id: I2adc0fb8846c4690f8eaac3bb80e6dbf25077be3
|
|
phosphor-led-manager changed to use json configuration by default.
However, Mt.Mitchell still uses yaml configuration which consequently
fail to parse for platform LED configuration.
This commit changes configuration from yaml to json to adapt upstream
codes.
Tested:
1. Check if all LED Groups are created, the same as using yaml file
root@mtmitchell-dcscm:~# busctl tree xyz.openbmc_project.LED.GroupManager
`- /xyz
`- /xyz/openbmc_project
`- /xyz/openbmc_project/led
`- /xyz/openbmc_project/led/groups
|- /xyz/openbmc_project/led/groups/bmc_booted
|- /xyz/openbmc_project/led/groups/power_on
|- /xyz/openbmc_project/led/groups/enclosure_identify
|- /xyz/openbmc_project/led/groups/enclosure_identify_blink
`- /xyz/openbmc_project/led/groups/systemFault
2. Check if no error message in journal log
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Ibdc2a566d89d8d661f299aff84539e471061090a
|
