Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: 2.18.0-dev
# ec075823 05-Sep-2024 Chanh Nguyen <chanh@os.amperecomputing.com>

meta-ampere: Update LED configurations

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

meta-ampere: Update LED configurations

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

show more ...


# 3d40352f 23-Aug-2024 Alexander Hansen <alexander.hansen@9elements.com>

update configurations for phosphor-led-manager

phosphor-led-manager no longer assumes any default led priority.

The behavior was changed in

https://github.com/openbmc/phosphor-led-manager/commit/5

update configurations for phosphor-led-manager

phosphor-led-manager no longer assumes any default led priority.

The behavior was changed in

https://github.com/openbmc/phosphor-led-manager/commit/5a9f651949c133ed0868d72734c4ac82c75a7656
and
https://github.com/openbmc/phosphor-led-manager/commit/55badf7979f57d5f9ed2db726eebf35e84d0dac5

The led priority needs to be configured, so updating all configurations
here.

Before, led-manager assumed a default led priority of 'Blink'.

So this patch is just making that explicit in the existing
configurations. There should be no behavior change from this patch.

Change-Id: I74aabb567ccf6682d56877f8bb42e636fc1746f6
Signed-off-by: Alexander Hansen <alexander.hansen@9elements.com>

show more ...


Revision tags: 2.17.0-dev
# 0b6e1c09 29-Jan-2024 Hieu Huynh <hieuh@os.amperecomputing.com>

meta-ampere: mtjade: separate FAN Led group for each FAN

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 FA

meta-ampere: mtjade: separate FAN Led group for each FAN

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: Ic48fb402266bd3b95263ba8278e2f50d3bbb3bfe

show more ...


# 95a21774 27-Jan-2024 Hieu Huynh <hieuh@os.amperecomputing.com>

meta-ampere: mtjade: update LED configuration file name

phosphor-led-manager is changed to use xyz.openbmc_project.Inventory.
Decorator.Compatible interface to select the configuration file.
This up

meta-ampere: mtjade: update LED configuration file name

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@mtjade:~# ls /usr/share/phosphor-led-manager/
com.ampere.Hardware.Chassis.Model.MtJade.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: I83647f465506d3fc3202d2b8f7145a1342f86dcf

show more ...