| /openbmc/u-boot/drivers/led/ |
| H A D | Kconfig | 1 menu "LED Support"
3 config LED config
4 bool "Enable LED support"
8 U-Boot provides a uclass API to implement this feature. LED drivers
13 bool "LED Support for BCM6328"
14 depends on LED && ARCH_BMIPS
17 LED HW controller accessed via MMIO registers.
20 means that if one LED is set to blink at 100ms and then a different
21 LED is set to blink at 200ms, both will blink at 200ms.
24 bool "LED Support for BCM6358"
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.LED | 1 Status LED
4 This README describes the status LED API.
9 > Device Drivers > LED Support.
11 If the LED support is only for specific board, enable
23 CONFIG_STATUS_LED_BIT is passed into the __led_* functions to identify which LED
25 the other CONFIG_STATUS_LED_BIT's. Mapping the value to a physical LED is the
28 CONFIG_STATUS_LED_STATE is the initial state of the LED. It should be set to one
31 CONFIG_STATUS_LED_FREQ determines the LED blink frequency.
34 Some other LED macros
37 CONFIG_STATUS_LED_BOOT is the LED to light when the board is booting.
[all …]
|
| H A D | README.LED_display | 1 LED display internal API
4 This README describes the LED display API.
9 Then you need to provide the following functions to access LED display:
13 This function should control the state of the LED display. Argument is
20 This function should display it's parameter on the LED display in the
25 arguments on the LED display (or clear the display if called without
|
| /openbmc/docs/designs/ |
| H A D | multihost-physical-led.md | 1 # Physical LED Design Support
12 The existing phosphor-led-sysfs design exposes one service per LED configuration
20 For example, Power LED and System Identification LED combines into a single
21 bicolor blue-yellow LED per host. A total of 4 × LEDs will be placed along the
25 Depending on the status of each host, blue or yellow LED needs to be Blink, OFF
26 or ON and other LEDs needs to be in OFF state. Therefore, bi-color LED needs to
30 will be difficult, since it exposes one service per LED. To abstract this method
35 The below diagram represents the overview for current physical LED design.
38 KERNEL META-PHOSPHOR PHOSPHOR-LED-SYSFS SERVICE
40 +------------+ Event 1 +----------+ LED 1 +-----------------------------+
[all …]
|
| H A D | ocp-led-policy-support.md | 1 # OCP LED Policy Support
12 OpenBMC must support the [OCP LED Policy](#background-and-references). Currently
24 | 1 | 1 | LED Priority (cannot represent the fault state) |
35 When for example both of these groups are asserted, the change in LED state will
36 be determined by the LED priority. The result is not allowed in the state
47 Here we pretend that LED Priority "Off" is allowed and discover that it will not
59 #### LED Priority
69 | 0 | 0 | 0 | 1 | LED Priority (for reference) |
78 The different possible LED priorities do not matter here, since "Backup due to
80 LED Priority will prevent it from being applied completely when any other state
[all …]
|
| /openbmc/qemu/docs/interop/ |
| H A D | vnc-ledstate-pseudo-encoding.rst | 1 VNC LED state Pseudo-encoding
7 This document describes the Pseudo-encoding of LED state for RFB which
13 between the lock keys notification LED on the computer running the VNC
17 To solve this problem it attempts to add LED state Pseudo-encoding
18 extension to VNC protocol to deal with setting LED state.
24 LED state extensions to the protocol.
26 The Pseudo-encoding number for LED state defined as:
31 -261 'LED state Pseudo-encoding'
34 LED state Pseudo-encoding
37 The LED state Pseudo-encoding describes the encoding of LED state which
[all …]
|
| /openbmc/docs/architecture/ |
| H A D | LED-architecture.md | 1 # LED Support for OpenBMC
3 This document describes how to add LED support for your machine based upon the
4 OpenBMC [LED Architecture][led d-bus readme] document. LED group management is
11 Service xyx.openbmc_project.LED.GroupManager
25 The LED group state can be changed by setting the Asserted value to boolean 0
39 resource. This is for LED Identify operation only.
42 to LED Group D-Bus object, namely:
48 All applicable LED Group D-Bus objects would have an association mapping to
73 mapping to LED Group D-Bus object, namely;
79 All applicable LED Group D-Bus objects would have an association mapping to
[all …]
|
| /openbmc/u-boot/doc/device-tree-bindings/leds/ |
| H A D | common.txt | 4 - label : The label for this LED. If omitted, the label is
8 string defining the trigger assigned to the LED. Current triggers are:
9 "backlight" - LED will act as a back-light, controlled by the framebuffer
11 "default-on" - LED will turn on (but for leds-gpio see "default-state"
13 "heartbeat" - LED "double" flashes at a load average based rate
14 "ide-disk" - LED indicates disk activity
15 "timer" - LED flashes at a fixed, configurable rate
|
| H A D | leds-gpio.txt | 6 Each LED is represented as a sub-node of the gpio-leds device. Each
7 node's name represents the name of the corresponding LED.
9 LED sub-node properties:
10 - gpios : Should specify the LED's GPIO, see "gpios property" in
17 - default-state: (optional) The initial state of the LED. Valid
18 values are "on", "off", and "keep". If the LED is already on or off
20 glitch should be produced where the LED momentarily turns off (or
21 on). The "keep" setting will keep the LED at whatever its current
37 /* Keep LED on if BIOS detected hardware fault */
|
| H A D | leds-bcm6358.txt | 13 - reg : BCM6358 LED controller address and size.
21 Each LED is represented as a sub-node of the brcm,bcm6358-leds device.
23 LED sub-node required properties:
24 - reg : LED pin number (only LEDs 0 to 31 are valid).
26 LED sub-node optional properties:
28 - active-low : Boolean, makes LED active low.
|
| /openbmc/openbmc/meta-ampere/meta-common/recipes-phosphor/leds/ |
| H A D | phosphor-led-manager_%.bbappend | 4 file://LED-GroupManager-override.conf \
8 ${systemd_system_unitdir}/xyz.openbmc_project.LED.GroupManager.service.d \
14 install -d ${D}${systemd_system_unitdir}/xyz.openbmc_project.LED.GroupManager.service.d
15 install -m 644 ${UNPACKDIR}/LED-GroupManager-override.conf \
16 ${D}${systemd_system_unitdir}/xyz.openbmc_project.LED.GroupManager.service.d
|
| /openbmc/openbmc/meta-facebook/meta-ventura/recipes-phosphor/leds/ |
| H A D | phosphor-led-manager_%.bbappend | 4 file://xyz.openbmc_project.LED.GroupManager.service.d/override.conf\
7 FILES:${PN} += "${systemd_system_unitdir}/xyz.openbmc_project.LED.GroupManager.service.d"
10 install -d ${D}${systemd_system_unitdir}/xyz.openbmc_project.LED.GroupManager.service.d
11 install -m 0644 ${UNPACKDIR}/xyz.openbmc_project.LED.GroupManager.service.d/override.conf \
12 ${D}${systemd_system_unitdir}/xyz.openbmc_project.LED.GroupManager.service.d/
|
| /openbmc/openbmc-test-automation/redfish/systems/ |
| H A D | test_led_indicator_asserted.robot | 23 Verify LED Lamp Test Asserted At Standby
24 [Documentation] Verify the LED asserted at standby is set to off or blinking.
26 [Template] Set and Verify Lamp LED Indicator
33 Verify LED Lamp Test Asserted At Runtime
34 [Documentation] Verify the LED asserted at runtime is set to off or blinking.
36 [Template] Set and Verify Lamp LED Indicator
43 Verify LED Power Supply Units Asserted At Standby
46 [Template] Set and Verify LED Indicator
53 Verify LED Power Supply Units Asserted At Runtime
56 [Template] Set and Verify LED Indicator
[all …]
|
| /openbmc/phosphor-led-manager/ |
| H A D | README.md | 3 This project manages LED groups on dbus. Sometimes many LEDs must be driven
13 ### Configuration: LED Priority
15 Each LED can have "Priority" as "Blink", "Off" or "On". If this property is
16 defined, it should be defined on each instance of the LED in the config.
18 When multiple LED groups are asserted and contain the same LED, "Priority"
19 determines the state of the LED.
24 ## Configuration: LED Group Priority
26 Using LED Priority is fine for simple configurations, but when group state needs
127 When starting the program, our LED group shows up on dbus. Usually there will be
131 $ busctl tree xyz.openbmc_project.LED.GroupManager
[all …]
|
| /openbmc/s2600wf-misc/subprojects/callback-manager/ |
| H A D | README.md | 13 We need a centralized location to change the LED state.
23 Need to be able to trigger the LED from multiple locations and maintain state.
27 The callback manager can change LED state in the below ways.
34 state, and a component health state. We need to map these to the LED.
38 Warning thresholds will trigger warning (blink green) LED state.
56 If the path for an association is Critical for Global & Local, the LED will be
60 the LED will be in the Critical (amber blink) state.
63 local, the LED will be in the Warning (blink green) state.
67 Write the LED manually, this seems very error prone.
75 Sensor override, then look at LED and Redfish.
|
| /openbmc/s2600wf-misc/callback-manager/ |
| H A D | README.md | 13 We need a centralized location to change the LED state.
23 Need to be able to trigger the LED from multiple locations and maintain state.
27 The callback manager can change LED state in the below ways.
34 state, and a component health state. We need to map these to the LED.
38 Warning thresholds will trigger warning (blink green) LED state.
56 If the path for an association is Critical for Global & Local, the LED will be
60 the LED will be in the Critical (amber blink) state.
63 local, the LED will be in the Warning (blink green) state.
67 Write the LED manually, this seems very error prone.
75 Sensor override, then look at LED and Redfish.
|
| /openbmc/phosphor-led-sysfs/ |
| H A D | README.md | 7 Say we have 'identify' LED in our system, which may be declared in devicetree.
19 We can add an LED via the helper program. The main service is then started via
29 busctl tree xyz.openbmc_project.LED.Controller
36 busctl introspect xyz.openbmc_project.LED.Controller /xyz/openbmc_project/led/physical/identify
51 Query the LED State
54 busctl get-property xyz.openbmc_project.LED.Controller \
60 Set the LED State
63 busctl set-property xyz.openbmc_project.LED.Controller \
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Led/ |
| H A D | README.md | 1 # Managing LED groups and physical LEDs through BMC
9 ## Understanding LED groups
11 While it is entirely possible to act directly on a physical LED, it makes hard
12 when more than one LED is to be acted on for a particular usecase.
15 LED upon reaching some state. However, some other systems may have a requirement
26 requirement of blinking system Enclosure LED indicating an internal problem:
29 that system before acting on it. In one case, the LED group may consist of DIMM
30 LED + Enclosure Fault LED. However, if the DIMM is attached to a Raiser card,
31 then the LED group may consist of DIMM LED + Raise card LED + Enclosure Fault
32 LED. Defining this path will make it easier to locate the box and the exact part
[all …]
|
| /openbmc/phosphor-led-manager/service_files/ |
| H A D | obmc-led-group-start@.service | 2 Description=Assert %i LED
3 Wants=xyz.openbmc_project.LED.GroupManager.service
4 After=xyz.openbmc_project.LED.GroupManager.service
11 ExecStart=/bin/sh -c "busctl set-property xyz.openbmc_project.LED.GroupManager /xyz/openbmc_project…
|
| H A D | obmc-led-group-stop@.service | 2 Description=Deassert %i LED
3 Wants=xyz.openbmc_project.LED.GroupManager.service
4 After=xyz.openbmc_project.LED.GroupManager.service
11 ExecStart=/bin/sh -c "busctl set-property xyz.openbmc_project.LED.GroupManager /xyz/openbmc_project…
|
| /openbmc/phosphor-led-manager/scripts/ |
| H A D | led-set-all-groups-asserted.sh | 55 …for line in $(busctl tree xyz.openbmc_project.LED.GroupManager | grep -e groups/ | awk -F 'xyz' '{…
57 …busctl set-property xyz.openbmc_project.LED.GroupManager "$line" xyz.openbmc_project.Led.Group Ass…
60 …for line in $(busctl tree xyz.openbmc_project.LED.GroupManager | grep -e groups/ | grep -Ev "$excl…
62 …busctl set-property xyz.openbmc_project.LED.GroupManager "$line" xyz.openbmc_project.Led.Group Ass…
|
| /openbmc/u-boot/board/eets/pdu001/ |
| H A D | Kconfig | 21 prompt "State of Run LED"
24 The PDU001 has a bi-color (red/green) LED labeled 'Run' which
34 Lit Run LED red.
40 Lit Run LED green.
46 Do not lit Run LED.
|
| /openbmc/openbmc/meta-quanta/meta-gbs/recipes-gbs/boot-status-led/files/ |
| H A D | boot-status-led.service | 2 Description=Boot Status LED Manager
3 After=xyz.openbmc_project.LED.GroupManager.service
4 Wants=xyz.openbmc_project.LED.GroupManager.service
|
| /openbmc/openbmc/meta-quanta/meta-gbs/recipes-phosphor/leds/ |
| H A D | phosphor-led-manager_%.bbappend | 4 FILES:${PN}:append:gbs = " ${systemd_system_unitdir}/xyz.openbmc_project.LED.GroupManager.service.d…
9 install -d ${D}${systemd_system_unitdir}/xyz.openbmc_project.LED.GroupManager.service.d
11 ${D}${systemd_system_unitdir}/xyz.openbmc_project.LED.GroupManager.service.d/
|
| /openbmc/openbmc-test-automation/gui/gui_test/overview_menu/ |
| H A D | test_overview_menu.robot | 154 Verify Server LED Turn On
155 [Documentation] Turn on server LED via GUI and verify its status via Redfish.
158 # Turn Off the server LED via Redfish and refresh GUI.
162 # Turn ON the LED via GUI.
165 # Cross check that server LED ON state via Redfish.
166 Verify Identify LED State Via Redfish Lit
169 Verify Server LED Turn Off
170 [Documentation] Turn off server LED via GUI and verify its status via Redfish.
173 # Turn On the server LED via Redfish and refresh GUI.
177 # Turn OFF the LED via GUI.
[all …]
|