Home
last modified time | relevance | path

Searched +full:default +full:- +full:trigger (Results 1 – 25 of 1071) sorted by relevance

12345678910>>...43

/linux-5.10/arch/arm/boot/dts/
Dbcm47081-luxul-xwr-1200.dts1 // 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 …]
Domap5-uevm.dts1 // 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 …]
Dbcm4708-smartrg-sr400ac.dts1 // 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 …]
Dbcm4708-buffalo-wzr-1750dhp.dts1 // 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 …]
Dbcm4708-netgear-r6250.dts5 * Copyright 2013 Hauke Mehrtens <hauke@hauke-m.de>
10 /dts-v1/;
13 #include "bcm5301x-nand-cs0-bch8.dtsi"
30 compatible = "gpio-leds";
35 linux,default-trigger = "default-on";
41 linux,default-trigger = "default-on";
52 trigger-sources = <&ohci_port1>, <&ehci_port1>,
54 linux,default-trigger = "usbport";
63 gpio-keys {
64 compatible = "gpio-keys";
[all …]
Dbcm47081-tplink-archer-c5-v2.dts1 // 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";
36 usb2-port1 {
37 label = "bcm53xx:green:usb2-port1";
39 trigger-sources = <&ohci_port1>, <&ehci_port1>;
40 linux,default-trigger = "usbport";
46 linux,default-trigger = "default-on";
[all …]
Dimx7d-meerkat96.dts1 // SPDX-License-Identifier: GPL-2.0+ OR MIT
6 /dts-v1/;
12 compatible = "novtech,imx7d-meerkat96", "fsl,imx7d";
15 stdout-path = &uart6;
23 reg_wlreg_on: regulator-wlreg-on {
24 compatible = "regulator-fixed";
25 pinctrl-names = "default";
26 pinctrl-0 = <&pinctrl_wlreg_on>;
27 regulator-name = "wlreg_on";
28 regulator-min-microvolt = <3300000>;
[all …]
Dbcm4709-tplink-archer-c9-v1.dts1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
6 /dts-v1/;
11 compatible = "tplink,archer-c9-v1", "brcm,bcm4709", "brcm,bcm4708";
12 model = "TP-LINK Archer C9 V1";
24 compatible = "gpio-leds";
49 trigger-sources = <&ohci_port1>, <&ehci_port1>,
51 linux,default-trigger = "usbport";
57 trigger-sources = <&ohci_port2>, <&ehci_port2>;
58 linux,default-trigger = "usbport";
61 wan-blue {
[all …]
Darmada-388-helios4.dts1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)
10 /dts-v1/;
11 #include "armada-388.dtsi"
12 #include "armada-38x-solidrun-microsom.dtsi"
25 /* So that mvebu u-boot can update the MAC addresses */
30 stdout-path = "serial0:115200n8";
33 reg_12v: regulator-12v {
34 compatible = "regulator-fixed";
35 regulator-name = "power_brick_12V";
36 regulator-min-microvolt = <12000000>;
[all …]
Daks-cdu.dts1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * aks-cdu.dts - Device Tree file for AK signal CDU
9 /dts-v1/;
11 #include "ge863-pro3.dtsi"
20 clock-frequency = <32768>;
32 linux,rs485-enabled-at-boot-time;
33 rs485-rts-delay = <0 0>;
38 linux,rs485-enabled-at-boot-time;
39 rs485-rts-delay = <0 0>;
44 linux,rs485-enabled-at-boot-time;
[all …]
Dam572x-idk-common.dtsi1 // SPDX-License-Identifier: GPL-2.0
3 * Copyright (C) 2017 Texas Instruments Incorporated - https://www.ti.com/
6 #include <dt-bindings/gpio/gpio.h>
7 #include <dt-bindings/interrupt-controller/irq.h>
8 #include "am57xx-idk-common.dtsi"
9 #include "dra74-ipu-dsp-common.dtsi"
17 reserved-memory {
18 #address-cells = <2>;
19 #size-cells = <2>;
22 ipu2_memory_region: ipu2-memory@95800000 {
[all …]
Dbcm47094-luxul-xwr-3150-v1.dts1 // SPDX-License-Identifier: GPL-2.0-or-later OR MIT
6 /dts-v1/;
9 #include "bcm5301x-nand-cs0-bch8.dtsi"
12 compatible = "luxul,xwr-3150-v1", "brcm,bcm47094", "brcm,bcm4708";
13 model = "Luxul XWR-3150 V1";
26 compatible = "gpio-leds";
31 linux,default-trigger = "default-on";
37 trigger-sources = <&ohci_port1>, <&ehci_port1>,
39 linux,default-trigger = "usbport";
45 linux,default-trigger = "timer";
[all …]
Dat91-kizbox.dts1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * at91-kizbox.dts - Device Tree file for Overkiz Kizbox board
5 * Copyright (C) 2012-2014 Boris BREZILLON <b.brezillon@overkiz.com>
6 * 2014-2015 Gaël PORTAY <g.portay@overkiz.com>
8 /dts-v1/;
10 #include <dt-bindings/pwm/pwm.h>
18 stdout-path = &dbgu;
27 clock-frequency = <18432000>;
32 compatible = "gpio-keys";
33 #address-cells = <1>;
[all …]
Dexynos54xx-odroidxu-leds.dtsi1 // SPDX-License-Identifier: GPL-2.0
11 #include <dt-bindings/gpio/gpio.h>
15 compatible = "pwm-leds";
20 pwm-names = "pwm1";
26 linux,default-trigger = "mmc0";
32 pwm-names = "pwm2";
34 linux,default-trigger = "heartbeat";
39 compatible = "gpio-leds";
43 default-state = "off";
44 linux,default-trigger = "mmc1";
/linux-5.10/Documentation/leds/
Dledtrig-transient.rst2 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 …]
/linux-5.10/arch/arm64/boot/dts/rockchip/
Drk3399-rock960.dts1 // 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 …]
Drk3399-ficus.dts1 // 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 …]
/linux-5.10/arch/arm64/boot/dts/freescale/
Dimx8qxp-ai_ml.dts1 // 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 …]
/linux-5.10/Documentation/devicetree/bindings/leds/
Dpca963x.txt4 - 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 …]
Dcommon.yaml1 # 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 …]
Dregister-bit-led.txt10 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 …]
/linux-5.10/Documentation/iio/
Diio_configfs.rst8 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 …]
/linux-5.10/include/linux/
Dleds.h1 /* 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 …]
/linux-5.10/Documentation/devicetree/bindings/arm/
Dcoresight-cti.yaml1 # SPDX-License-Identifier: GPL-2.0-only or BSD-2-Clause
4 ---
5 $id: http://devicetree.org/schemas/arm/coresight-cti.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: ARM Coresight Cross Trigger Interface (CTI) device.
11 The CoreSight Embedded Cross Trigger (ECT) consists of CTI devices connected
13 a star topology via the Cross Trigger Matrix (CTM), which is not programmable.
20 output hardware trigger signals. CTIs can have a maximum number of input and
21 output hardware trigger signals (8 each for v1 CTI, 32 each for v2 CTI). The
31 In general the connections between CTI and components via the trigger signals
[all …]
/linux-5.10/Documentation/trace/coresight/
Dcoresight-ect.rst1 .. SPDX-License-Identifier: GPL-2.0
4 CoreSight Embedded Cross Trigger (CTI & CTM).
11 --------------------
13 The CoreSight Cross Trigger Interface (CTI) is a hardware device that takes
15 devices and interconnects them via the Cross Trigger Matrix (CTM) to other
21 0 C 0----------->: : +======>(other CTI channel IO)
22 0 P 0<-----------: : v
24 0000000 : CTI :<=========>*CTM*<====>: CTI :---+
25 ####### in_trigs : : (id 0-3) ***** ::::::: v
26 # ETM #----------->: : ^ #######
[all …]

12345678910>>...43