Home
last modified time | relevance | path

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

123456789

/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 …]
Dleds-class.rst8 of the LED (taking a value 0-max_brightness). Most LEDs don't have hardware
9 brightness support so will just be turned on for non-zero brightness settings.
11 The class also introduces the optional concept of an LED trigger. A trigger
13 complex. A simple trigger isn't configurable and is designed to slot into
14 existing subsystems with minimal additional code. Examples are the disk-activity,
15 nand-disk and sharpsl-charge triggers. With led triggers disabled, the code
19 parameters and work on a per LED basis. The timer trigger is an example.
20 The timer trigger will periodically change the LED brightness between
24 trigger. However, if you set the brightness value to LED_OFF it will
25 also disable the timer trigger.
[all …]
Dleds-blinkm.rst5 The leds-blinkm driver supports the devices of the BlinkM family.
7 They are RGB-LED modules driven by a (AT)tiny microcontroller and
8 communicate through I2C. The default address of these modules is
10 daisy-chain up to 127 BlinkMs on an I2C bus.
16 The interface this driver provides is 3-fold:
23 blinkm-<i2c-bus-nr>-<i2c-device-nr>:rgb:indicator
25 $ ls -h /sys/class/leds/blinkm-1-9:rgb:indicator
26 …brightness device max_brightness multi_index multi_intensity power subsystem trigger uevent
45 blinkm-<i2c-bus-nr>-<i2c-device-nr>-<color>
47 $ ls -h /sys/class/leds/blinkm-6-*
[all …]
/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 …]
/Documentation/devicetree/bindings/power/reset/
Dltc2952-poweroff.txt3 This chip is used to externally trigger a system shut down. Once the trigger has
9 - compatible: Must contain: "lltc,ltc2952"
10 - watchdog-gpios: phandle + gpio-specifier for the GPIO connected to the
12 - kill-gpios: phandle + gpio-specifier for the GPIO connected to the
16 - trigger-gpios: phandle + gpio-specifier for the GPIO connected to the
17 chip's trigger line. If this property is not set, the
18 trigger function is ignored and the chip is kept alive
20 - trigger-delay-ms The number of milliseconds to wait after trigger line
22 The default is 2500ms.
29 trigger-gpios = <&gpio0 1 GPIO_ACTIVE_LOW>;
[all …]
/Documentation/devicetree/bindings/leds/
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 …]
Dleds-lt3593.txt4 - compatible: Should be "lltc,lt3593".
5 - lltc,ctrl-gpios: A handle to the GPIO that is connected to the 'CTRL'
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.
18 - default-state: The initial state of the LED.
26 #include <dt-bindings/leds/common.h>
[all …]
Dregulator-led.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/regulator-led.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
20 - $ref: common.yaml#
27 const: regulator-led
29 vled-supply:
35 linux,default-trigger: true
36 default-state: true
[all …]
Dleds-mt6323.txt5 PMIC controller that is being defined as one kind of Muti-Function Device (MFD)
15 - compatible : Must be one of
16 - "mediatek,mt6323-led"
17 - "mediatek,mt6331-led"
18 - "mediatek,mt6332-led"
19 - address-cells : Must be 1
20 - size-cells : Must be 0
22 Each led is represented as a child node of the mediatek,mt6323-led that
27 - reg : LED channel number (0..3)
30 - label : See Documentation/devicetree/bindings/leds/common.txt
[all …]
Dleds-lm3697.txt1 * Texas Instruments - LM3697 Highly Efficient White LED Driver
3 The LM3697 11-bit LED driver provides high-
10 - compatible:
12 - reg : I2C slave address
13 - #address-cells : 1
14 - #size-cells : 0
17 - enable-gpios : GPIO pin to enable/disable the device
18 - vled-supply : LED supply
21 - reg : 0 - LED is Controlled by bank A
22 1 - LED is Controlled by bank B
[all …]
Dleds-lp8860.txt1 * Texas Instruments - lp8860 4-Channel LED Driver
3 The LP8860-Q1 is an high-efficiency LED
4 driver with boost controller. It has 4 high-precision
9 - compatible :
11 - reg : I2C slave address
12 - #address-cells : 1
13 - #size-cells : 0
16 - enable-gpios : gpio pin to enable (active high)/disable the device.
17 - vled-supply : LED supply
20 - reg : 0
[all …]
Dleds-pca955x.txt1 * NXP - pca955x LED driver
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
23 LED sub-node properties:
[all …]
Dleds-ns2.txt1 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
15 Optional sub-node properties:
16 - label: Name for this LED. If omitted, the label is taken from the node name.
[all …]
Dleds-lm36274.txt1 * Texas Instruments LM36274 4-Channel LCD Backlight Driver w/Integrated Bias
3 The LM36274 is an integrated four-channel WLED driver and LCD bias supply.
5 up to 29V total output voltage. The 11-bit LED current is programmable via
9 Documentation/devicetree/bindings/mfd/ti-lmu.txt
12 Documentation/devicetree/bindings/regulator/lm363x-regulator.txt
15 - compatible:
16 "ti,lm36274-backlight"
17 - reg : 0
18 - #address-cells : 1
19 - #size-cells : 0
[all …]
/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 …]
/Documentation/admin-guide/media/
Dmgb4.rst1 .. SPDX-License-Identifier: GPL-2.0
7 ---------------
13 There are two types of parameters - global / PCI card related, found under
23 | 0 - No module present
24 | 1 - FPDL3
25 | 2 - GMSL
33 | 1 - FPDL3
34 | 2 - GMSL
42 PRODUCT-REVISION-SERIES-SERIAL
55 | 0 - single
[all …]
/Documentation/ABI/testing/
Dsysfs-class-led9 just be turned on for non-zero brightness settings.
23 Documentation/leds/leds-class-multicolor.rst.
28 Writing 0 to this file clears active trigger.
30 Writing non-zero to this file while trigger is active changes the
31 top brightness trigger is going to use.
40 Maximum brightness level for this LED, default is 255 (LED_FULL).
62 What: /sys/class/leds/<led>/trigger
67 Set the trigger for this LED. A trigger is a kernel based source
71 scheduler is chosen. Trigger specific parameters can appear in
72 /sys/class/leds/<led> once a given trigger is selected. For
[all …]
Dsysfs-driver-w1_therm7 (typical -55 degC to 125 degC), if not values will be trimmed
11 master level, refer to Documentation/w1/w1-generic.rst for
21 (WO) writing that file will either trigger a save of the
41 * '-xx': xx is kernel error when reading power status
54 power is lost. Trigger a 'save' to EEPROM command to keep
55 values after power-on. Read or write are :
59 * '-xx': xx is kernel error when reading the resolution
62 Some DS18B20 clones are fixed in 12-bit resolution, so the
80 * If no bulk read has been triggered, it will trigger
115 (RW) trigger a bulk read conversion. read the status
[all …]
/Documentation/devicetree/bindings/arm/
Darm,coresight-cti.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
4 ---
5 $id: http://devicetree.org/schemas/arm/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.
19 output hardware trigger signals. CTIs can have a maximum number of input and
20 output hardware trigger signals (8 each for v1 CTI, 32 each for v2 CTI). The
30 In general the connections between CTI and components via the trigger signals
[all …]
/Documentation/fault-injection/
Dprovoke-crashes.rst1 .. SPDX-License-Identifier: GPL-2.0
11 trigger location, but can also trigger the kernel directly without KPROBE
14 You can select the location of the trigger ("crash point name") and the
24 Recursion level for the stack overflow test. By default this is
30 Where in the kernel to trigger the action. It can be
38 See the contents of `/sys/kernel/debug/provoke-crash/DIRECT` for
43 before triggering the action. The default is 10 (except for
47 <debugfs>/provoke-crash/<crashpoint>. E.g.::
49 mount -t debugfs debugfs /sys/kernel/debug
50 echo EXCEPTION > /sys/kernel/debug/provoke-crash/INT_HARDWARE_ENTRY
[all …]
/Documentation/devicetree/bindings/spi/
Dcdns,qspi-nor.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/spi/cdns,qspi-nor.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Vaishnav Achath <vaishnav.a@ti.com>
13 - $ref: spi-controller.yaml#
14 - if:
18 const: xlnx,versal-ospi-1.0
21 - power-domains
22 - if:
[all …]
/Documentation/misc-devices/
Dapds990x.rst1 .. SPDX-License-Identifier: GPL-2.0
17 -----------
39 values are known. Otherwise plain sensor default values are used.
48 -----
52 RO - shows detected chip type and version
55 RW - enable / disable chip. Uses counting logic
60 RO - measured lux value
65 RO - lux0_input max value.
72 RW - measurement rate in Hz
75 RO - supported measurement rates
[all …]
/Documentation/devicetree/bindings/leds/backlight/
Darcxcnn_bl.txt4 - compatible: should be "arc,arc2c0608"
5 - reg: slave address
8 - default-brightness: brightness value on boot, value from: 0-4095
9 - label: The name of the backlight device
11 - led-sources: List of enabled channels from 0 to 5.
14 - arc,led-config-0: setting for register ILED_CONFIG_0
15 - arc,led-config-1: setting for register ILED_CONFIG_1
16 - arc,dim-freq: PWM mode frequence setting (bits [3:0] used)
17 - arc,comp-config: setting for register CONFIG_COMP
18 - arc,filter-config: setting for register FILTER_CONFIG
[all …]
/Documentation/admin-guide/perf/
Dhisi-pcie-pmu.rst15 The PCIe PMU driver registers a perf PMU with the name of its sicl-id and PCIe
40 ------------------------------------------
42 $# perf stat -e hisi_pcie0_core0/rx_mwr_latency,port=0xffff/
43 $# perf stat -e hisi_pcie0_core0/rx_mwr_cnt,port=0xffff/
56 …$# perf stat -e "{hisi_pcie0_core0/rx_mwr_latency,port=0xffff/,hisi_pcie0_core0/rx_mwr_cnt,port=0x…
62 --------------
72 If "port" filter not being set or is set explicitly to zero (default), the
75 - port
78 selected by configuring the 16-bits-bitmap "port". Multi ports can be
79 selected for AP-layer-events, and only one port can be selected for
[all …]
/Documentation/devicetree/bindings/pinctrl/
Dpincfg-node.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/pincfg-node.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
21 bias-disable:
25 bias-high-impedance:
27 description: high impedance mode ("third-state", "floating")
29 bias-bus-hold:
33 bias-pull-up:
[all …]

123456789