| /openbmc/openbmc/meta-quanta/meta-gbs/recipes-phosphor/sensors/phosphor-nvme/ |
| H A D | nvme_config.json | 6 "NVMeDriveFaultLEDGroupPath": "/xyz/openbmc_project/led/groups/led_u2_0_fault",
7 "NVMeDriveLocateLEDGroupPath": "/xyz/openbmc_project/led/groups/led_u2_0_locate",
8 … "NVMeDriveLocateLEDControllerBusName": "xyz.openbmc_project.LED.Controller.led_u2_0_locate",
9 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_0_locate",
16 "NVMeDriveFaultLEDGroupPath": "/xyz/openbmc_project/led/groups/led_u2_1_fault",
17 "NVMeDriveLocateLEDGroupPath": "/xyz/openbmc_project/led/groups/led_u2_1_locate",
18 … "NVMeDriveLocateLEDControllerBusName": "xyz.openbmc_project.LED.Controller.led_u2_1_locate",
19 "NVMeDriveLocateLEDControllerPath": "/xyz/openbmc_project/led/physical/led_u2_1_locate",
26 "NVMeDriveFaultLEDGroupPath": "/xyz/openbmc_project/led/groups/led_u2_2_fault",
27 "NVMeDriveLocateLEDGroupPath": "/xyz/openbmc_project/led/groups/led_u2_2_locate",
[all …]
|
| H A D | nvme_json_rewrite.sh | 6 if [ ! -d "/sys/class/gpio/gpio$1" ]; then
12 # 1-0024
15 # 1-0021
17 if [ -d "/sys/bus/i2c/drivers/pca953x/1-0024" ]; then
18 presentPinBase="$(cat /sys/bus/i2c/drivers/pca953x/1-0024/gpio/gpiochip*/base)"
27 if [ -d "/sys/bus/i2c/drivers/pca953x/1-0021" ]; then
28 PwrGoodPinBase="$(cat /sys/bus/i2c/drivers/pca953x/1-0021/gpio/gpiochip*/base)"
43 "NVMeDriveFaultLEDGroupPath": "/xyz/openbmc_project/led/groups/led_u2_0_fault",
44 "NVMeDriveLocateLEDGroupPath": "/xyz/openbmc_project/led/groups/led_u2_0_locate",
45 … "NVMeDriveLocateLEDControllerBusName": "xyz.openbmc_project.LED.Controller.led_u2_0_locate",
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-led-flash | 1 What: /sys/class/leds/<led>/flash_brightness
6 Set the brightness of this LED in the flash strobe mode, in
7 microamperes. The file is created only for the flash LED devices
11 /sys/class/leds/<led>/max_flash_brightness.
13 What: /sys/class/leds/<led>/max_flash_brightness
18 Maximum brightness level for this LED in the flash strobe mode,
21 What: /sys/class/leds/<led>/flash_timeout
28 of the strobe. The file is created only for the flash LED
31 What: /sys/class/leds/<led>/max_flash_timeout
36 Maximum flash timeout for this LED, in microseconds.
[all …]
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | ext-ctrls-flash.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _flash-controls:
10 controller devices. Flash controller devices are typically used in
13 The interface can support both LED and xenon flash devices. As of
17 .. _flash-controls-use-cases:
23 Unsynchronised LED flash (software strobe)
24 ------------------------------------------
26 Unsynchronised LED flash is controlled directly by the host as the
34 Synchronised LED flash (hardware strobe)
35 ----------------------------------------
[all …]
|
| /openbmc/linux/arch/mips/boot/dts/mti/ |
| H A D | sead3.dts | 1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
8 #include <dt-bindings/interrupt-controller/mips-gic.h>
11 #address-cells = <1>;
12 #size-cells = <1>;
13 compatible = "mti,sead-3";
14 model = "MIPS SEAD-3";
17 stdout-path = "serial1:115200";
36 cpu_intc: interrupt-controller {
37 compatible = "mti,cpu-interrupt-controller";
[all …]
|
| /openbmc/linux/arch/arm/boot/dts/aspeed/ |
| H A D | aspeed-bmc-ibm-blueridge.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 /dts-v1/;
5 #include <dt-bindings/gpio/aspeed-gpio.h>
6 #include <dt-bindings/i2c/i2c.h>
7 #include <dt-bindings/leds/leds-pca955x.h>
8 #include "aspeed-g6.dtsi"
9 #include "ibm-power11-quad.dtsi"
13 compatible = "ibm,blueridge-bmc", "aspeed,ast2600";
35 stdout-path = &uart5;
43 reserved-memory {
[all …]
|
| H A D | aspeed-bmc-ibm-fuji.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 /dts-v1/;
5 #include <dt-bindings/gpio/aspeed-gpio.h>
6 #include <dt-bindings/i2c/i2c.h>
7 #include <dt-bindings/leds/leds-pca955x.h>
8 #include "aspeed-g6.dtsi"
9 #include "ibm-power11-quad.dtsi"
13 compatible = "ibm,fuji-bmc", "aspeed,ast2600";
170 stdout-path = &uart5;
178 reserved-memory {
[all …]
|
| H A D | aspeed-bmc-ibm-rainier.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 /dts-v1/;
5 #include "aspeed-g6.dtsi"
6 #include <dt-bindings/gpio/aspeed-gpio.h>
7 #include <dt-bindings/i2c/i2c.h>
8 #include <dt-bindings/leds/leds-pca955x.h>
12 compatible = "ibm,rainier-bmc", "aspeed,ast2600";
34 stdout-path = &uart5;
43 reserved-memory {
44 #address-cells = <1>;
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/leds/ |
| H A D | leds-lgm.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-lgm.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Intel Lightning Mountain (LGM) SoC LED Serial Shift Output (SSO) Controller driver
10 - Zhu, Yi Xin <Yixin.zhu@intel.com>
11 - Amireddy Mallikarjuna reddy <mallikarjunax.reddy@intel.com>
15 const: intel,lgm-ssoled
23 clock-names:
25 - const: sso
[all …]
|
| H A D | leds-bcm6328.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-bcm6328.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: LEDs connected to Broadcom BCM6328 controller
10 - Álvaro Fernández Rojas <noltari@gmail.com>
13 This controller is present on BCM6318, BCM6328, BCM6362 and BCM63268.
16 controller), which can either be controlled by software (exporting the 74x164
17 as spi-gpio. See
21 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
[all …]
|
| H A D | ti,tca6507.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TCA6507 LED and GPIO controller
10 - NeilBrown <neilb@suse.de>
13 The TCA6507 is a programmable LED controller connected via I2C that can drive
22 description: I2C slave address of the controller.
25 "#address-cells":
28 "#size-cells":
31 gpio-controller: true
[all …]
|
| H A D | leds-sc27xx-bltc.txt | 1 LEDs connected to Spreadtrum SC27XX PMIC breathing light controller
3 The SC27xx breathing light controller supports to 3 outputs:
4 red LED, green LED and blue LED. Each LED can work at normal
8 - compatible: Should be "sprd,sc2731-bltc".
9 - #address-cells: Must be 1.
10 - #size-cells: Must be 0.
11 - reg: Specify the controller address.
14 - reg: Port this LED is connected to.
17 - function: See Documentation/devicetree/bindings/leds/common.txt.
18 - color: See Documentation/devicetree/bindings/leds/common.txt.
[all …]
|
| H A D | leds-bcm6358.txt | 1 LEDs connected to Broadcom BCM6358 controller
3 This controller is present on BCM6358 and BCM6368.
4 In these SoCs there are Serial LEDs (LEDs connected to a 74x164 controller),
5 which can either be controlled by software (exporting the 74x164 as spi-gpio.
10 - compatible : should be "brcm,bcm6358-leds".
11 - #address-cells : must be 1.
12 - #size-cells : must be 0.
13 - reg : BCM6358 LED controller address and size.
16 - brcm,clk-div : SCK signal divider. Possible values are 1, 2, 4 and 8.
18 - brcm,clk-dat-low : Boolean, makes clock and data signals active low.
[all …]
|
| H A D | panasonic,an30259a.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Panasonic AN30259A 3-channel LED controller
10 - Iskren Chernev <me@iskren.info>
13 The AN30259A is a LED controller capable of driving three LEDs independently.
27 "#address-cells":
30 "#size-cells":
34 "^led@[1-3]$":
43 - compatible
[all …]
|
| H A D | leds-mt6323.txt | 1 Device Tree Bindings for LED support on MT6323 PMIC
3 MT6323 LED controller is subfunction provided by MT6323 PMIC, so the LED
5 PMIC controller that is being defined as one kind of Muti-Function Device (MFD)
15 - compatible : Must be one of
16 - "mediatek,mt6323-led"
17 - "mediatek,mt6331-led"
18 - "mediatek,mt6332-led"
19 - address-cells : Must be 1
20 - size-cells : Must be 0
22 Each led is represented as a child node of the mediatek,mt6323-led that
[all …]
|
| /openbmc/docs/designs/ |
| H A D | multihost-physical-led.md | 1 # Physical LED Design Support
4 (Jayashree), [jayashree-d@hcl](mailto:jayashree-d@hcl.com)
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
29 Based on the current design in phosphor-led-sysfs application, pairing groups
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.
[all …]
|
| /openbmc/phosphor-led-sysfs/ |
| H A D | README.md | 1 # phosphor-led-sysfs
7 Say we have 'identify' LED in our system, which may be declared in devicetree.
11 compatible = "gpio-leds";
19 We can add an LED via the helper program. The main service is then started via
20 dbus-activation.
23 ./add-led-action --path /sys/class/leds/identify
29 busctl tree xyz.openbmc_project.LED.Controller
30 `- /xyz
31 `- /xyz/openbmc_project
32 `- /xyz/openbmc_project/led
[all …]
|
| /openbmc/linux/drivers/leds/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
10 bool "LED Support"
12 Say Y to enable Linux LED support. This allows control of supported
18 tristate "LED Class Support"
20 This option enables the LED sysfs class in /sys/class/leds. You'll
24 tristate "LED Flash Class Support"
27 This option enables the flash LED sysfs class in /sys/class/leds.
28 It wraps LED Class and adds flash LEDs specific sysfs attributes
30 for the flash related features of a LED device. It can be built
34 tristate "LED Multicolor Class Support"
[all …]
|
| /openbmc/linux/drivers/leds/flash/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
6 tristate "LED support for the AAT1290"
15 tristate "AS3645A and LM3555 LED flash controllers support"
19 Enable LED flash class support for AS3645A LED flash
20 controller. V4L2 flash API is provided as well if
24 tristate "LED support for Kinetic KTD2692 flash LED controller"
28 This option enables support for Kinetic KTD2692 LED flash connected
34 tristate "LED support for LM3601x Chips"
42 tristate "LED support for MAX77693 Flash"
52 tristate "LED Support for Mediatek MT6360 PMIC"
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/mfd/ |
| H A D | mediatek,mt6360.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Gene Chen <gene_chen@richtek.com>
14 It is interfaced to host controller using I2C interface.
25 wakeup-source: true
30 interrupt-names:
33 interrupt-controller: true
35 "#interrupt-cells":
41 $ref: /schemas/regulator/mt6360-regulator.yaml#
[all …]
|
| H A D | mediatek,mt6370.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - ChiYuan Huang <cy_huang@richtek.com>
13 MT6370 is a highly-integrated smart power management IC, which includes a
14 single cell Li-Ion/Li-Polymer switching battery charger, a USB Type-C &
15 Power Delivery (PD) controller, dual flash LED current sources, a RGB LED
26 wakeup-source: true
31 interrupt-controller: true
33 "#interrupt-cells":
[all …]
|
| /openbmc/u-boot/doc/device-tree-bindings/leds/ |
| H A D | leds-bcm6328.txt | 1 LEDs connected to Broadcom BCM6328 controller
3 This controller is present on BCM6318, BCM6328, BCM6362 and BCM63268.
6 controller), which can either be controlled by software (exporting the 74x164
7 as spi-gpio. See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or
10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
14 - compatible : should be "brcm,bcm6328-leds".
15 - #address-cells : must be 1.
16 - #size-cells : must be 0.
17 - reg : BCM6328 LED controller address and size.
20 - brcm,serial-leds : Boolean, enables Serial LEDs.
[all …]
|
| H A D | leds-bcm6358.txt | 1 LEDs connected to Broadcom BCM6358 controller
3 This controller is present on BCM6358 and BCM6368.
4 In these SoCs there are Serial LEDs (LEDs connected to a 74x164 controller),
5 which can either be controlled by software (exporting the 74x164 as spi-gpio.
6 See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or
10 - compatible : should be "brcm,bcm6358-leds".
11 - #address-cells : must be 1.
12 - #size-cells : must be 0.
13 - reg : BCM6358 LED controller address and size.
16 - brcm,clk-div : SCK signal divider. Possible values are 1, 2, 4 and 8.
[all …]
|
| /openbmc/u-boot/arch/nds32/cpu/n1213/ag101/ |
| H A D | lowlevel_init.S | 1 /* SPDX-License-Identifier: GPL-2.0+ */
16 #include <generated/asm-offsets.h>
19 * parameters for the SDRAM controller
46 * parameters for the static memory controller
55 * parameters for the ahbc controller
74 .macro led, num macro
98 led 0x01
116 /* 32-bit mode */
121 /* 16-bit mode */
130 /* config AHB Controller */
[all …]
|
| /openbmc/linux/arch/arm/boot/dts/arm/ |
| H A D | arm-realview-eb.dtsi | 23 #include <dt-bindings/interrupt-controller/irq.h>
24 #include <dt-bindings/gpio/gpio.h>
27 #address-cells = <1>;
28 #size-cells = <1>;
29 compatible = "arm,realview-eb";
49 compatible = "regulator-fixed";
50 regulator-name = "vmmc";
51 regulator-min-microvolt = <3300000>;
52 regulator-max-microvolt = <3300000>;
53 regulator-boot-on;
[all …]
|