| /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 …]
|
| H A D | sysfs-class-scsi_host | 6 SCU controller. The Intel(R) C600 Series Chipset SATA/SAS 7 Storage Control Unit embeds up to two 4-port controllers in 10 with the first controller, but this association is not 12 the controller index: '0' for the first controller, 24 '1' indicates the feature is enabled, and the controller may 26 means the feature is disabled and the controller may not use 28 controller wide, affecting all configured logical drives on the 29 controller. This file is readable and writable. 34 Contact: linux-ide@vger.kernel.org 41 min_power: Tell the controller to try to make the link use the [all …]
|
| /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 …]
|
| /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 | 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-lt3593.txt | 1 Bindings for Linear Technologies LT3593 LED controller 4 - compatible: Should be "lltc,lt3593". 5 - lltc,ctrl-gpios: A handle to the GPIO that is connected to the 'CTRL' 8 The hardware supports only one LED. The properties of this LED are 9 configured in a sub-node in the device node. 11 Optional sub-node properties: 12 - function: See Documentation/devicetree/bindings/leds/common.txt 13 - color: See Documentation/devicetree/bindings/leds/common.txt 14 - label: A label for the LED. If none is given, the LED will be 16 - linux,default-trigger: The default trigger for the LED. [all …]
|
| H A D | rohm,bd2606mvv.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: ROHM BD2606MVV LED controller 10 - Andreas Kemnade <andreas@kemnade.info> 13 The BD2606 MVV is a programmable LED controller connected via I2C that can 18 https://fscdn.rohm.com/en/products/databook/datasheet/ic/power/led_driver/bd2606mvv_1-e.pdf 27 "#address-cells": 30 "#size-cells": 33 enable-gpios: [all …]
|
| H A D | leds-aw2013.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/leds/leds-aw2013.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: AWINIC AW2013 3-channel LED Driver 10 - Nikita Travkin <nikitos.tr@gmail.com> 13 The AW2013 is a 3-channel LED driver with I2C interface. It can control 14 LED brightness with PWM output. 25 description: Open-drain, low active interrupt pin "INTN". 26 Used to report completion of operations (power up, LED breath effects). [all …]
|
| H A D | leds-mt6360.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/leds/leds-mt6360.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: LED driver for MT6360 PMIC from MediaTek Integrated. 10 - Gene Chen <gene_chen@richtek.com> 15 Add MT6360 LED driver include 2-channel Flash LED with torch/strobe mode, 16 and 4-channel RGB LED support Register/Flash/Breath Mode 20 const: mediatek,mt6360-led 22 "#address-cells": [all …]
|
| H A D | kinetic,ktd202x.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Kinetic KTD2026/7 RGB/White LED Driver 10 - André Apitzsch <git@apitzsch.eu> 13 The KTD2026/7 is a RGB/White LED driver with I2C interface. 16 https://www.kinet-ic.com/uploads/KTD2026-7-04h.pdf 21 - kinetic,ktd2026 22 - kinetic,ktd2027 27 vin-supply: [all …]
|
| H A D | leds-rt4505.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/leds/leds-rt4505.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Richtek RT4505 Single Channel LED Driver 10 - ChiYuan Huang <cy_huang@richtek.com> 13 The RT4505 is a flash LED driver that can support up to 375mA and 1.5A for 17 https://www.richtek.com/assets/product_file/RT4505/DS4505-02.pdf 24 description: I2C slave address of the controller. 27 led: [all …]
|
| H A D | nxp,pca955x.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: NXP PCA955X LED controllers 10 - Nate Case <ncase@xes-inc.com> 13 The PCA955x family of chips are I2C LED blinkers whose pins not used 15 be input or output, and output pins can also be pulse-width controlled. 18 - https://www.nxp.com/docs/en/data-sheet/PCA9552.pdf 23 - nxp,pca9550 24 - nxp,pca9551 [all …]
|
| /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 …]
|
| /linux/arch/arm/boot/dts/aspeed/ |
| 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 …]
|
| H A D | aspeed-bmc-ibm-balcones.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-dual.dtsi" 13 compatible = "ibm,balcones-bmc", "aspeed,ast2600"; 24 stdout-path = &uart5; 27 gpio-keys-polled { [all …]
|
| H A D | aspeed-bmc-ibm-system1.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,system1-bmc", "aspeed,ast2600"; 74 stdout-path = "uart5:115200n8"; 82 reserved-memory { 83 #address-cells = <1>; [all …]
|
| /linux/arch/arm/boot/dts/qcom/ |
| H A D | pm8058.dtsi | 1 // SPDX-License-Identifier: GPL-2.0 6 #interrupt-cells = <2>; 7 interrupt-controller; 8 #address-cells = <1>; 9 #size-cells = <0>; 12 compatible = "qcom,pm8058-pwrkey"; 14 interrupts-extended = <&pm8058 50 IRQ_TYPE_EDGE_RISING>, 17 pull-up; 20 pm8058_led48: led@48 { 21 compatible = "qcom,pm8058-keypad-led"; [all …]
|
| /linux/arch/arm/boot/dts/arm/ |
| H A D | versatile-ab.dts | 1 // SPDX-License-Identifier: GPL-2.0 2 /dts-v1/; 6 compatible = "arm,versatile-ab"; 7 #address-cells = <1>; 8 #size-cells = <1>; 9 interrupt-parent = <&vic>; 19 stdout-path = &uart0; 27 xtal24mhz: clock-24000000 { 28 #clock-cells = <0>; 29 compatible = "fixed-clock"; [all …]
|
| /linux/arch/arm/boot/dts/samsung/ |
| H A D | exynos54xx-odroidxu-leds.dtsi | 1 // SPDX-License-Identifier: GPL-2.0 3 * Hardkernel Odroid XU/XU3 LED device tree source 11 #include <dt-bindings/gpio/gpio.h> 12 #include <dt-bindings/leds/common.h> 15 led-controller-1 { 16 compatible = "pwm-leds"; 18 led-1 { 23 pwm-names = "pwm1"; 25 * Green LED is much brighter than the others 28 max-brightness = <127>; [all …]
|
| /linux/arch/arm/boot/dts/marvell/ |
| H A D | armada-xp-netgear-rn2120.dts | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT) 8 /dts-v1/; 10 #include <dt-bindings/input/input.h> 11 #include <dt-bindings/gpio/gpio.h> 12 #include "armada-xp-mv78230.dtsi" 16 …compatible = "netgear,readynas-2120", "marvell,armadaxp-mv78230", "marvell,armadaxp", "marvell,arm… 19 stdout-path = "serial0:115200n8"; 33 internal-regs { 41 clock-frequency = <400000>; 44 /* Controller for rear fan #1 of 3 (Protechnic [all …]
|
| /linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | brcm,nsp-gpio.txt | 1 Broadcom Northstar plus (NSP) GPIO/PINCONF Controller 4 - compatible: 5 Must be "brcm,nsp-gpio-a" 7 - reg: 11 - #gpio-cells: 13 controller's pin space) and the second cell is used for the following: 16 - gpio-controller: 17 Specifies that the node is a GPIO controller 19 - ngpios: 23 - interrupts: [all …]
|
| /linux/Documentation/leds/ |
| H A D | well-known-leds.txt | 1 -*- org -*- 4 userland. LED devices have one problem there, and that is naming of 6 just know right "name" for given LED function, but situation got more 17 Notice there's a list of functions in include/dt-bindings/leds/common.h . 24 player. For example, a game controller with 4 LEDs, may be programmed with "x---" 25 to indicate player 1, "-x--" to indicate player 2 etcetera where "x" means on. 26 Input drivers can utilize the LED class to expose the individual player LEDs 27 of a game controller using the function "player". 31 Good: "input*:*:player-{1,2,3,4,5} 38 Legacy: "shift-key-light" (Motorola Droid 4, capslock) [all …]
|