Searched +full:led +full:- +full:order (Results 1 – 25 of 517) sorted by relevance
12345678910>>...21
| /kernel/linux/linux-5.10/Documentation/leds/ |
| D | leds-class-flash.rst | 2 Flash LED handling under Linux 5 Some LED devices provide two modes - torch and flash. In the LED subsystem 6 those modes are supported by LED class (see Documentation/leds/leds-class.rst) 7 and LED Flash class respectively. The torch mode related features are enabled 11 In order to enable the support for flash LEDs CONFIG_LEDS_CLASS_FLASH symbol 12 must be defined in the kernel config. A LED Flash class driver must be 13 registered in the LED subsystem with led_classdev_flash_register function. 15 Following sysfs attributes are exposed for controlling flash LED devices: 16 (see Documentation/ABI/testing/sysfs-class-led-flash) 18 - flash_brightness [all …]
|
| D | leds-class-multicolor.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 Multicolor LED handling under Linux 17 array. These files are children under the LED parent node created by the 18 led_class framework. The led_class framework is documented in led-class.rst 21 Each colored LED will be indexed under the multi_* files. The order of the 30 order for the color LED intensities to be updated. 34 root:/sys/class/leds/multicolor:status# ls -lR 35 -rw-r--r-- 1 root root 4096 Oct 19 16:16 brightness 36 -r--r--r-- 1 root root 4096 Oct 19 16:16 max_brightness 37 -r--r--r-- 1 root root 4096 Oct 19 16:16 multi_index [all …]
|
| /kernel/linux/linux-6.6/Documentation/leds/ |
| D | leds-class-flash.rst | 2 Flash LED handling under Linux 5 Some LED devices provide two modes - torch and flash. In the LED subsystem 6 those modes are supported by LED class (see Documentation/leds/leds-class.rst) 7 and LED Flash class respectively. The torch mode related features are enabled 11 In order to enable the support for flash LEDs CONFIG_LEDS_CLASS_FLASH symbol 12 must be defined in the kernel config. A LED Flash class driver must be 13 registered in the LED subsystem with led_classdev_flash_register function. 15 Following sysfs attributes are exposed for controlling flash LED devices: 16 (see Documentation/ABI/testing/sysfs-class-led-flash) 18 - flash_brightness [all …]
|
| D | leds-class-multicolor.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 Multicolor LED handling under Linux 17 array. These files are children under the LED parent node created by the 18 led_class framework. The led_class framework is documented in led-class.rst 21 Each colored LED will be indexed under the multi_* files. The order of the 30 order for the color LED intensities to be updated. 34 root:/sys/class/leds/multicolor:status# ls -lR 35 -rw-r--r-- 1 root root 4096 Oct 19 16:16 brightness 36 -r--r--r-- 1 root root 4096 Oct 19 16:16 max_brightness 37 -r--r--r-- 1 root root 4096 Oct 19 16:16 multi_index [all …]
|
| D | leds-qcom-lpg.rst | 1 .. SPDX-License-Identifier: GPL-2.0 8 ----------- 11 number of PWM channels, a programmable pattern lookup table and a RGB LED 22 In order to provide support for status notifications with the CPU subsystem in 30 /sys/class/leds/<led>/hw_pattern 31 -------------------------------- 33 Specify a hardware pattern for a Qualcomm LPG LED. 35 The pattern is a series of brightness and hold-time pairs, with the hold-time 39 transitions expected by the leds-trigger-pattern format, each entry in the 40 pattern must be followed a zero-length entry of the same brightness. [all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/gpio/ |
| D | board.rst | 7 Note that it only applies to the new descriptor-based interface. For a 8 description of the deprecated integer-based GPIO interface please refer to 9 gpio-legacy.txt (actually, there is no real mapping possible with the old 20 ----------- 26 <function>-gpios, where <function> is the function the driver will request 32 led-gpios = <&gpio 15 GPIO_ACTIVE_HIGH>, /* red */ 36 power-gpios = <&gpio 1 GPIO_ACTIVE_LOW>; 39 Properties named <function>-gpio are also considered valid and old bindings use 44 "led" function, and GPIO 1 as the "power" GPIO:: 48 red = gpiod_get_index(dev, "led", 0, GPIOD_OUT_HIGH); [all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/gpio/ |
| D | board.rst | 7 Note that it only applies to the new descriptor-based interface. For a 8 description of the deprecated integer-based GPIO interface please refer to 20 ----------- 26 <function>-gpios, where <function> is the function the driver will request 32 led-gpios = <&gpio 15 GPIO_ACTIVE_HIGH>, /* red */ 36 power-gpios = <&gpio 1 GPIO_ACTIVE_LOW>; 39 Properties named <function>-gpio are also considered valid and old bindings use 44 "led" function, and GPIO 1 as the "power" GPIO:: 48 red = gpiod_get_index(dev, "led", 0, GPIOD_OUT_HIGH); 49 green = gpiod_get_index(dev, "led", 1, GPIOD_OUT_HIGH); [all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/ |
| D | leds-ns2.txt | 1 Binding for dual-GPIO LED found on Network Space v2 (and parents). 4 - compatible: "lacie,ns2-leds". 6 Each LED is represented as a sub-node of the ns2-leds device. 8 Required sub-node properties: 9 - cmd-gpio: Command LED GPIO. See OF device-tree GPIO specification. 10 - slow-gpio: Slow LED GPIO. See OF device-tree GPIO specification. 11 - modes-map: A mapping between LED modes (off, on or SATA activity blinking) and 12 the corresponding cmd-gpio/slow-gpio values. All the GPIO values combinations 13 should be given in order to avoid having an unknown mode at driver probe time. 15 Optional sub-node properties: [all …]
|
| D | leds-aat1290.txt | 5 respectively. In order to add a capability of selecting the strobe signal source 11 - compatible : Must be "skyworks,aat1290". 12 - flen-gpios : Must be device tree identifier of the flash device FL_EN pin. 13 - enset-gpios : Must be device tree identifier of the flash device EN_SET pin. 16 - pinctrl-names : Must contain entries: "default", "host", "isp". Entries 22 A discrete LED element connected to the device must be represented by a child 23 node - see Documentation/devicetree/bindings/leds/common.txt. 25 Required properties of the LED child node: 26 - led-max-microamp : see Documentation/devicetree/bindings/leds/common.txt 27 - flash-max-microamp : see Documentation/devicetree/bindings/leds/common.txt [all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/leds/ |
| D | leds-ns2.txt | 1 Binding for dual-GPIO LED found on Network Space v2 (and parents). 4 - compatible: "lacie,ns2-leds". 6 Each LED is represented as a sub-node of the ns2-leds device. 8 Required sub-node properties: 9 - cmd-gpio: Command LED GPIO. See OF device-tree GPIO specification. 10 - slow-gpio: Slow LED GPIO. See OF device-tree GPIO specification. 11 - modes-map: A mapping between LED modes (off, on or SATA activity blinking) and 12 the corresponding cmd-gpio/slow-gpio values. All the GPIO values combinations 13 should be given in order to avoid having an unknown mode at driver probe time. 15 Optional sub-node properties: [all …]
|
| D | skyworks,aat1290.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Jacek Anaszewski <jacek.anaszewski@gmail.com> 11 - Krzysztof Kozlowski <krzk@kernel.org> 16 respectively. In order to add a capability of selecting the strobe signal 24 enset-gpios: 28 flen-gpios: 32 led: 37 led-max-microamp: true [all …]
|
| /kernel/linux/linux-5.10/drivers/mfd/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 44 tristate "Active-semi ACT8945A" 49 Support for the ACT8945A PMIC from Active-semi. This device 50 features three step-down DC/DC converters and four low-dropout 66 sun4i-gpadc-iio and the hwmon driver iio_hwmon. 69 called sun4i-gpadc. 88 tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down 110 additional drivers must be enabled in order to use the 119 over at91-usart-serial driver and usart-spi-driver. Only one function 135 tristate "Atmel HLCDC (High-end LCD Controller)" [all …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-class-led-multicolor | 2 What: /sys/class/leds/<led>/multi_index 7 The multi_index array, when read, will output the LED colors 12 Documentation/leds/leds-class-multicolor.rst. 14 What: /sys/class/leds/<led>/multi_intensity 19 This file contains array of integers. Order of components is 21 not exceed /sys/class/leds/<led>/max_brightness. 24 Documentation/leds/leds-class-multicolor.rst.
|
| D | sysfs-class-scsi_host | 7 Storage Control Unit embeds up to two 4-port controllers in 8 a single PCI device. The controllers are enumerated in order 34 Contact: linux-ide@vger.kernel.org 60 a) It does not use host-initiated slumber mode, but it does 61 allow device-initiated slumber 68 Contact: linux-ide@vger.kernel.org 70 em_message: (RW) Enclosure management support. For the LED 71 protocol, writes and reads correspond to the LED message format 75 OFF it they wish to control the activity LED via the em_message 79 protocol that is being used by the driver (for eg. LED, SAF-TE, [all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-class-led-multicolor | 2 What: /sys/class/leds/<led>/multi_index 7 The multi_index array, when read, will output the LED colors 12 Documentation/leds/leds-class-multicolor.rst. 14 What: /sys/class/leds/<led>/multi_intensity 19 This file contains array of integers. Order of components is 21 not exceed /sys/class/leds/<led>/max_brightness. 24 Documentation/leds/leds-class-multicolor.rst.
|
| D | sysfs-class-scsi_host | 7 Storage Control Unit embeds up to two 4-port controllers in 8 a single PCI device. The controllers are enumerated in order 34 Contact: linux-ide@vger.kernel.org 60 a) It does not use host-initiated slumber mode, but it does 61 allow device-initiated slumber 68 Contact: linux-ide@vger.kernel.org 70 em_message: (RW) Enclosure management support. For the LED 71 protocol, writes and reads correspond to the LED message format 75 OFF it they wish to control the activity LED via the em_message 79 protocol that is being used by the driver (for eg. LED, SAF-TE, [all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/net/wireless/ |
| D | mediatek,mt76.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 2 # Copyright (c) 2018-2019 The Linux Foundation. All rights reserved. 4 --- 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 - Felix Fietkau <nbd@nbd.name> 12 - Lorenzo Bianconi <lorenzo@kernel.org> 13 - Ryder Lee <ryder.lee@mediatek.com> 23 - $ref: ieee80211.yaml# 28 - mediatek,mt76 29 - mediatek,mt7628-wmac [all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| D | philips.rst | 1 .. SPDX-License-Identifier: GPL-2.0 7 E-mail: webcam@smcc.demon.nl Last updated: 2004-01-19 30 * Samsung MPC-C10 31 * Samsung MPC-C30 33 * AME CU-001 34 * Visionite VCS-UM100 35 * Visionite VCS-UC300 46 the latter, since it makes troubleshooting a lot easier. The built-in 50 camera; some programs depend on a particular image-size or -format and 60 Specifies the desired framerate. Is an integer in the range of 4-30. [all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/media/ |
| D | philips.rst | 1 .. SPDX-License-Identifier: GPL-2.0 7 E-mail: webcam@smcc.demon.nl Last updated: 2004-01-19 30 * Samsung MPC-C10 31 * Samsung MPC-C30 33 * AME CU-001 34 * Visionite VCS-UM100 35 * Visionite VCS-UC300 46 the latter, since it makes troubleshooting a lot easier. The built-in 50 camera; some programs depend on a particular image-size or -format and 60 Specifies the desired framerate. Is an integer in the range of 4-30. [all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/ata/ |
| D | sata_highbank.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 15 - Andre Przywara <andre.przywara@arm.com> 19 const: calxeda,hb-ahci 27 dma-coherent: true 29 calxeda,pre-clocks: 35 calxeda,post-clocks: 41 calxeda,led-order: 43 $ref: /schemas/types.yaml#/definitions/uint32-array [all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/ata/ |
| D | sata_highbank.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 15 - Andre Przywara <andre.przywara@arm.com> 19 const: calxeda,hb-ahci 27 dma-coherent: true 29 calxeda,pre-clocks: 35 calxeda,post-clocks: 41 calxeda,led-order: 43 $ref: /schemas/types.yaml#/definitions/uint32-array [all …]
|
| /kernel/linux/linux-6.6/drivers/mfd/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 45 tristate "Active-semi ACT8945A" 50 Support for the ACT8945A PMIC from Active-semi. This device 51 features three step-down DC/DC converters and four low-dropout 67 sun4i-gpadc-iio and the hwmon driver iio_hwmon. 70 called sun4i-gpadc. 101 tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down 123 additional drivers must be enabled in order to use the 132 over at91-usart-serial driver and usart-spi-driver. Only one function 148 tristate "Atmel HLCDC (High-end LCD Controller)" [all …]
|
| /kernel/linux/linux-6.6/arch/arm/boot/dts/broadcom/ |
| D | bcm47094-dlink-dir-890l.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT 3 * Device tree for D-Link DIR-890L 4 * D-Link calls this board "WRGAC36" 5 * this router has the same looks and form factor as D-Link DIR-885L. 7 * Some differences from DIR-885L include a separate USB2 port, separate LEDs 11 * order. 13 * Based on the device tree for DIR-885L 18 /dts-v1/; 21 #include "bcm5301x-nand-cs0-bch1.dtsi" 24 compatible = "dlink,dir-890l", "brcm,bcm47094", "brcm,bcm4708"; [all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | max77693.txt | 1 Maxim MAX77693 multi-function device 4 - PMIC, 5 - CHARGER, 6 - LED, 7 - MUIC, 8 - HAPTIC 14 - compatible : Must be "maxim,max77693". 15 - reg : Specifies the i2c slave address of PMIC block. 16 - interrupts : This i2c device has an IRQ line connected to the main SoC. 19 - regulators : The regulators of max77693 have to be instantiated under subnode [all …]
|
| /kernel/linux/linux-6.6/arch/arm/boot/dts/st/ |
| D | stm32mp15xx-dhcom-picoitx.dtsi | 1 // SPDX-License-Identifier: GPL-2.0+ OR BSD-3-Clause 6 #include <dt-bindings/input/input.h> 7 #include <dt-bindings/pwm/pwm.h> 10 led { 11 compatible = "gpio-leds"; 13 led-0 { 14 label = "yellow:led"; 16 default-state = "off"; 37 * in order to turn on port power when USB bus is powered up, but so 40 usb-port-power-hog { [all …]
|
12345678910>>...21