| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | bcm47081-luxul-xwr-1200.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT 6 /dts-v1/; 9 #include "bcm5301x-nand-cs0-bch4.dtsi" 12 compatible = "luxul,xwr-1200v1", "brcm,bcm47081", "brcm,bcm4708"; 13 model = "Luxul XWR-1200 V1"; 25 compatible = "gpio-leds"; 30 linux,default-trigger = "default-on"; 36 linux,default-trigger = "none"; 42 linux,default-trigger = "none"; 48 linux,default-trigger = "none"; [all …]
|
| D | omap5-uevm.dts | 1 // SPDX-License-Identifier: GPL-2.0-only 3 * Copyright (C) 2013 Texas Instruments Incorporated - https://www.ti.com/ 5 /dts-v1/; 7 #include "omap5-board-common.dtsi" 11 compatible = "ti,omap5-uevm", "ti,omap5"; 18 reserved-memory { 19 #address-cells = <2>; 20 #size-cells = <2>; 23 dsp_memory_region: dsp-memory@95000000 { 24 compatible = "shared-dma-pool"; [all …]
|
| D | bcm4708-smartrg-sr400ac.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT 9 /dts-v1/; 12 #include "bcm5301x-nand-cs0-bch8.dtsi" 29 compatible = "gpio-leds"; 31 power-white { 34 linux,default-trigger = "default-on"; 37 power-amber { 45 trigger-sources = <&ohci_port2>, <&ehci_port2>; 46 linux,default-trigger = "usbport"; 49 usb3-white { [all …]
|
| D | bcm4708-buffalo-wzr-1750dhp.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT 4 * DTS for Buffalo WZR-1750DHP 9 /dts-v1/; 12 #include "bcm5301x-nand-cs0-bch8.dtsi" 15 compatible = "buffalo,wzr-1750dhp", "brcm,bcm4708"; 16 model = "Buffalo WZR-1750DHP (BCM4708)"; 29 compatible = "spi-gpio"; 30 num-chipselects = <1>; 31 gpio-sck = <&chipcommon 7 0>; 32 gpio-mosi = <&chipcommon 4 0>; [all …]
|
| /kernel/linux/linux-6.6/arch/arm/boot/dts/broadcom/ |
| D | bcm47081-luxul-xwr-1200.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT 6 /dts-v1/; 9 #include "bcm5301x-nand-cs0-bch4.dtsi" 12 compatible = "luxul,xwr-1200-v1", "brcm,bcm47081", "brcm,bcm4708"; 13 model = "Luxul XWR-1200 V1"; 29 #nvmem-cell-cells = <1>; 34 compatible = "gpio-leds"; 36 led-power { 39 linux,default-trigger = "default-on"; 42 led-lan3 { [all …]
|
| D | bcm4708-smartrg-sr400ac.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT 9 /dts-v1/; 12 #include "bcm5301x-nand-cs0-bch8.dtsi" 29 compatible = "gpio-leds"; 31 led-power-white { 34 linux,default-trigger = "default-on"; 37 led-power-amber { 42 led-usb2 { 45 trigger-sources = <&ohci_port2>, <&ehci_port2>; 46 linux,default-trigger = "usbport"; [all …]
|
| D | bcm4708-buffalo-wzr-1750dhp.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT 4 * DTS for Buffalo WZR-1750DHP 9 /dts-v1/; 12 #include "bcm5301x-nand-cs0-bch8.dtsi" 15 compatible = "buffalo,wzr-1750dhp", "brcm,bcm4708"; 16 model = "Buffalo WZR-1750DHP (BCM4708)"; 29 compatible = "spi-gpio"; 30 num-chipselects = <1>; 31 sck-gpios = <&chipcommon 7 0>; 32 mosi-gpios = <&chipcommon 4 0>; [all …]
|
| D | bcm47081-tplink-archer-c5-v2.dts | 1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT 6 /dts-v1/; 11 compatible = "tplink,archer-c5-v2", "brcm,bcm47081", "brcm,bcm4708"; 12 model = "TP-LINK Archer C5 V2"; 24 compatible = "gpio-leds"; 26 led-2ghz { 31 led-lan { 36 led-usb2-port1 { 37 label = "bcm53xx:green:usb2-port1"; 39 trigger-sources = <&ohci_port1>, <&ehci_port1>; [all …]
|
| /kernel/linux/linux-5.10/Documentation/leds/ |
| D | ledtrig-transient.rst | 2 LED Transient Trigger 5 The leds timer trigger does not currently have an interface to activate 10 should stay in off state. The on and off cycle repeats until the trigger 15 Without one shot timer interface, user space can still use timer trigger to 20 Transient trigger addresses the need for one shot timer activation. The 21 transient trigger can be enabled and disabled just like the other leds 25 triggers it supports and a default trigger. During registration, activation 26 routine for the default trigger gets called. During registration of an led 30 trigger will be called, and LED state is changed to LED_OFF. 34 suspend and resume actions and the currently enabled trigger. LED state [all …]
|
| /kernel/linux/linux-6.6/Documentation/leds/ |
| D | ledtrig-transient.rst | 2 LED Transient Trigger 5 The leds timer trigger does not currently have an interface to activate 10 should stay in off state. The on and off cycle repeats until the trigger 15 Without one shot timer interface, user space can still use timer trigger to 20 Transient trigger addresses the need for one shot timer activation. The 21 transient trigger can be enabled and disabled just like the other leds 25 triggers it supports and a default trigger. During registration, activation 26 routine for the default trigger gets called. During registration of an led 30 trigger will be called, and LED state is changed to LED_OFF. 34 suspend and resume actions and the currently enabled trigger. LED state [all …]
|
| /kernel/linux/linux-6.6/arch/arm/boot/dts/ti/omap/ |
| D | omap5-uevm.dts | 1 // SPDX-License-Identifier: GPL-2.0-only 3 * Copyright (C) 2013 Texas Instruments Incorporated - https://www.ti.com/ 5 /dts-v1/; 7 #include "omap5-board-common.dtsi" 11 compatible = "ti,omap5-uevm", "ti,omap5"; 18 reserved-memory { 19 #address-cells = <2>; 20 #size-cells = <2>; 23 dsp_memory_region: dsp-memory@95000000 { 24 compatible = "shared-dma-pool"; [all …]
|
| /kernel/linux/linux-6.6/arch/arm64/boot/dts/rockchip/ |
| D | rk3399-rock960.dts | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT) 6 /dts-v1/; 7 #include "rk3399-rock960.dtsi" 14 stdout-path = "serial2:1500000n8"; 18 compatible = "gpio-leds"; 19 pinctrl-names = "default"; 20 pinctrl-0 = <&user_led1_pin>, <&user_led2_pin>, 24 user_led1: led-1 { 27 linux,default-trigger = "heartbeat"; 30 user_led2: led-2 { [all …]
|
| D | rk3399-ficus.dts | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT) 9 /dts-v1/; 10 #include "rk3399-rock960.dtsi" 17 stdout-path = "serial2:1500000n8"; 20 clkin_gmac: external-gmac-clock { 21 compatible = "fixed-clock"; 22 clock-frequency = <125000000>; 23 clock-output-names = "clkin_gmac"; 24 #clock-cells = <0>; 28 compatible = "gpio-leds"; [all …]
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/rockchip/ |
| D | rk3399-rock960.dts | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT) 6 /dts-v1/; 7 #include "rk3399-rock960.dtsi" 14 stdout-path = "serial2:1500000n8"; 18 compatible = "gpio-leds"; 19 pinctrl-names = "default"; 20 pinctrl-0 = <&user_led1_pin>, <&user_led2_pin>, 24 user_led1: led-1 { 27 linux,default-trigger = "heartbeat"; 30 user_led2: led-2 { [all …]
|
| D | rk3399-ficus.dts | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT) 9 /dts-v1/; 10 #include "rk3399-rock960.dtsi" 17 stdout-path = "serial2:1500000n8"; 20 clkin_gmac: external-gmac-clock { 21 compatible = "fixed-clock"; 22 clock-frequency = <125000000>; 23 clock-output-names = "clkin_gmac"; 24 #clock-cells = <0>; 28 compatible = "gpio-leds"; [all …]
|
| /kernel/linux/linux-6.6/arch/arm64/boot/dts/freescale/ |
| D | imx8qxp-ai_ml.dts | 1 // SPDX-License-Identifier: GPL-2.0+ 7 /dts-v1/; 13 compatible = "einfochips,imx8qxp-ai_ml", "fsl,imx8qxp"; 22 stdout-path = &lpuart2; 31 compatible = "gpio-leds"; 32 pinctrl-names = "default"; 33 pinctrl-0 = <&pinctrl_leds>; 35 user-led1 { 38 linux,default-trigger = "heartbeat"; 41 user-led2 { [all …]
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/freescale/ |
| D | imx8qxp-ai_ml.dts | 1 // SPDX-License-Identifier: GPL-2.0+ 7 /dts-v1/; 13 compatible = "einfochips,imx8qxp-ai_ml", "fsl,imx8qxp"; 22 stdout-path = &adma_lpuart2; 31 compatible = "gpio-leds"; 32 pinctrl-names = "default"; 33 pinctrl-0 = <&pinctrl_leds>; 35 user-led1 { 38 linux,default-trigger = "heartbeat"; 41 user-led2 { [all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/ |
| D | pca963x.txt | 4 - compatible : should be : "nxp,pca9632", "nxp,pca9633", "nxp,pca9634" or "nxp,pca9635" 7 - nxp,totem-pole : use totem pole (push-pull) instead of open-drain (pca9632 defaults 8 to open-drain, newer chips to totem pole) 9 - nxp,hw-blink : use hardware blinking instead of software blinking 10 - nxp,period-scale : In some configurations, the chip blinks faster than expected. 13 - nxp,inverted-out: invert the polarity of the generated PWM 15 Each led is represented as a sub-node of the nxp,pca963x device. 17 LED sub-node properties: 18 - label : (optional) see Documentation/devicetree/bindings/leds/common.txt 19 - reg : number of LED line (could be from 0 to 3 in pca9632 or pca9633, [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> 25 led-sources: 30 $ref: /schemas/types.yaml#definitions/uint32-array 35 from the header include/dt-bindings/leds/common.h. If there is no 42 the header include/dt-bindings/leds/common.h. If there is no matching 48 function-enumerator: [all …]
|
| D | register-bit-led.txt | 10 Each LED is represented as a sub-node of the syscon device. Each 13 LED sub-node properties: 16 - compatible : must be "register-bit-led" 17 - offset : register offset to the register controlling this LED 18 - mask : bit mask for the bit controlling this LED in the register 22 - label : (optional) 24 - linux,default-trigger : (optional) 26 - default-state: (optional) The initial state of the LED 32 compatible = "arm,realview-pb1176-syscon", "syscon"; 36 compatible = "register-bit-led"; [all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/leds/ |
| D | pca963x.txt | 4 - compatible : should be : "nxp,pca9632", "nxp,pca9633", "nxp,pca9634" or "nxp,pca9635" 7 - nxp,totem-pole : use totem pole (push-pull) instead of open-drain (pca9632 defaults 8 to open-drain, newer chips to totem pole) 9 - nxp,hw-blink : use hardware blinking instead of software blinking 10 - nxp,period-scale : In some configurations, the chip blinks faster than expected. 13 - nxp,inverted-out: invert the polarity of the generated PWM 15 Each led is represented as a sub-node of the nxp,pca963x device. 17 LED sub-node properties: 18 - label : (optional) see Documentation/devicetree/bindings/leds/common.txt 19 - reg : number of LED line (could be from 0 to 3 in pca9632 or pca9633, [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> 25 led-sources: 30 $ref: /schemas/types.yaml#/definitions/uint32-array 35 from the header include/dt-bindings/leds/common.h. If there is no 42 the header include/dt-bindings/leds/common.h. If there is no matching 48 function-enumerator: [all …]
|
| /kernel/linux/linux-6.6/Documentation/iio/ |
| D | iio_configfs.rst | 8 Configfs is a filesystem-based manager of kernel objects. IIO uses some 24 $ mount -t configfs none /config 26 At this point, all default IIO groups will be created and can be accessed 33 One of the IIO default configfs groups is the "triggers" group. It is 38 trigger types. A new trigger type is usually implemented as a separate 42 * drivers/iio/trigger/iio-trig-sample.c 43 * sample kernel module implementing a new trigger type 51 * This allocates and registers an IIO trigger plus other 52 * trigger type specific initialization. 69 .name = "trig-sample", [all …]
|
| /kernel/linux/linux-5.10/Documentation/iio/ |
| D | iio_configfs.rst | 8 Configfs is a filesystem-based manager of kernel objects. IIO uses some 24 $ mount -t configfs none /config 26 At this point, all default IIO groups will be created and can be accessed 33 One of the IIO default configfs groups is the "triggers" group. It is 38 trigger types. A new trigger type is usually implemented as a separate 42 * drivers/iio/trigger/iio-trig-sample.c 43 * sample kernel module implementing a new trigger type 51 * This allocates and registers an IIO trigger plus other 52 * trigger type specific initialization. 69 .name = "trig-sample", [all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | leds.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */ 11 #include <dt-bindings/leds/common.h> 40 * default <color:function> tuple, for backward compatibility 41 * with in-driver hard-coded LED names used as a fallback when 54 * only LEDs exposed by drivers of hot-pluggable devices should 100 * Set LED brightness level immediately - it can block the caller for 110 * and if both are zero then a sensible default should be chosen. 128 const char *default_trigger; /* Trigger to use */ 140 /* Protects the trigger data below */ 143 struct led_trigger *trigger; member [all …]
|