Searched +full:led +full:- +full:controller (Results 1 – 25 of 660) sorted by relevance
12345678910>>...27
/Linux-v5.15/Documentation/ABI/testing/ |
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 …]
|
/Linux-v5.15/Documentation/userspace-api/media/v4l/ |
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 …]
|
/Linux-v5.15/arch/mips/boot/dts/mti/ |
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-v5.15/drivers/leds/ |
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 …]
|
/Linux-v5.15/Documentation/devicetree/bindings/leds/ |
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 …]
|
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/fairchild,74hc595.yaml), 10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware 13 BCM6328 LED controller has a HWDIS register, which controls whether a LED 16 is usually 1:1 for hardware to LED signals, but through the activity/link 18 explained later in brcm,link-signal-sources). Even if a LED is hardware 21 reason, hardware controlled LEDs aren't registered as LED class devices. 24 - compatible : should be "brcm,bcm6328-leds". [all …]
|
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 …]
|
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 …]
|
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 …]
|
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 "mediatek,mt6323-led" 16 - address-cells : Must be 1 17 - size-cells : Must be 0 19 Each led is represented as a child node of the mediatek,mt6323-led that 20 describes the initial behavior for each LED physically and currently only four 21 LED child nodes can be supported. 23 Required properties for the LED child node: [all …]
|
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 …]
|
D | common.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Jacek Anaszewski <jacek.anaszewski@gmail.com> 11 - Pavel Machek <pavel@ucw.cz> 14 LED and flash LED devices provide the same basic functionality as current 15 regulators, but extended with LED and flash LED specific features like 18 Many LED devices expose more than one current output that can be connected 19 to one or more discrete LED component. Since the arrangement of connections 20 can influence the way of the LED device initialization, the LED components [all …]
|
D | cznic,turris-omnia-leds.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/leds/cznic,turris-omnia-leds.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Marek Behún <kabel@kernel.org> 15 microcontroller that communicates via the I2C bus. Each LED is described 20 const: cznic,turris-omnia-leds 26 "#address-cells": 29 "#size-cells": 33 "^multi-led@[0-9a-b]$": [all …]
|
D | leds-an30259a.txt | 1 * Panasonic AN30259A 3-channel LED driver 3 The AN30259A is a LED controller capable of driving three LEDs independently. It supports 7 - compatible: Must be "panasonic,an30259a". 8 - reg: I2C slave address. 9 - #address-cells: Must be 1. 10 - #size-cells: Must be 0. 12 Each LED is represented as a sub-node of the panasonic,an30259a node. 14 Required sub-node properties: 15 - reg: Pin that the LED is connected to. Must be 1, 2, or 3. 17 Optional sub-node properties: [all …]
|
D | leds-pca955x.txt | 1 * NXP - pca955x LED driver 3 The PCA955x family of chips are I2C LED blinkers whose pins not used 5 be input or output, and output pins can also be pulse-width controlled. 8 - compatible : should be one of : 14 - #address-cells: must be 1 15 - #size-cells: must be 0 16 - reg: I2C slave address. depends on the model. 19 - gpio-controller: allows pins to be used as GPIOs. 20 - #gpio-cells: must be 2. 21 - gpio-line-names: define the names of the GPIO lines [all …]
|
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 …]
|
/Linux-v5.15/drivers/leds/flash/ |
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 RT4505 flashlight controller" [all …]
|
/Linux-v5.15/arch/arm/boot/dts/ |
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; 28 #clock-cells = <0>; 29 compatible = "fixed-clock"; 30 clock-frequency = <24000000>; [all …]
|
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> 14 led-controller-1 { 15 compatible = "pwm-leds"; 17 led-1 { 20 pwm-names = "pwm1"; 22 * Green LED is much brighter than the others 25 max-brightness = <127>; 26 linux,default-trigger = "mmc0"; [all …]
|
D | arm-realview-pb1176.dts | 23 /dts-v1/; 24 #include <dt-bindings/interrupt-controller/irq.h> 25 #include <dt-bindings/gpio/gpio.h> 28 #address-cells = <1>; 29 #size-cells = <1>; 31 compatible = "arm,realview-pb1176"; 50 vmmc: regulator-vmmc { 51 compatible = "regulator-fixed"; 52 regulator-name = "vmmc"; 53 regulator-min-microvolt = <3300000>; [all …]
|
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 …]
|
D | aspeed-bmc-ibm-everest.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,everest-bmc", "aspeed,ast2600"; 137 stdout-path = &uart5; 146 reserved-memory { 147 #address-cells = <1>; [all …]
|
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 …]
|
/Linux-v5.15/Documentation/devicetree/bindings/pinctrl/ |
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-v5.15/Documentation/devicetree/bindings/mfd/ |
D | max77650.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: MAX77650 ultra low-power PMIC from Maxim Integrated. 10 - Bartosz Golaszewski <bgolaszewski@baylibre.com> 13 MAX77650 is an ultra-low power PMIC providing battery charging and power 14 supply for low-power IoT and wearable applications. 16 The GPIO-controller module is represented as part of the top-level PMIC 19 For device-tree bindings of other sub-modules (regulator, power supply, 21 sub-system directories. [all …]
|
12345678910>>...27