Searched full:trigger (Results 1 – 25 of 343) sorted by relevance
12345678910>>...14
| /Documentation/driver-api/iio/ |
| D | triggers.rst | 5 * struct :c:type:`iio_trigger` — industrial I/O trigger device 11 * :c:func:`iio_trigger_validate_own_device` — Check if a trigger and IIO 15 on some external event (trigger) as opposed to periodically polling for data. 16 An IIO trigger can be provided by a device driver that also has an IIO device 20 a specific file in sysfs). A trigger may initiate data capture for a number of 23 IIO trigger sysfs interface 28 * :file:`/sys/bus/iio/devices/trigger{Y}/*`, this file is created once an 29 IIO trigger is registered with the IIO core and corresponds to trigger 34 * :file:`name`, trigger name that can be later used for association with a 37 specify the frequency for trigger calls. [all …]
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | at91_adc.txt | 32 NOTE: when adc touchscreen is enabled, the adc hardware trigger will be 33 disabled. Since touchscreen will occupy the trigger register. 37 Optional trigger Nodes: 39 * trigger-name: Name of the trigger exposed to the user 40 * trigger-value: Value to put in the Trigger register 41 to activate this trigger 43 * trigger-external: Is the trigger an external trigger? 63 trigger-name = "external-rising"; 64 trigger-value = <0x1>; 65 trigger-external; [all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-trigger-sysfs | 5 This file is provided by the iio-trig-sysfs stand-alone trigger 7 driven driver, associated with this trigger, to capture data 9 automated testing or in situations, where other trigger methods 11 X is the IIO index of the trigger. 18 trigger. In order to associate the trigger with an IIO device 20 /sys/bus/iio/devices/iio:deviceY/trigger/current_trigger. 27 driver and it is used to activate the creation of a new trigger. 30 trigger. If the trigger with the specified id is already present 38 created trigger from the list of available triggers. In order to 40 associated file, representing the id of the trigger that needs [all …]
|
| D | sysfs-class-led | 11 Writing 0 to this file clears active trigger. 13 Writing non-zero to this file while trigger is active changes the 14 top brightness trigger is going to use. 43 What: /sys/class/leds/<led>/trigger 48 Set the trigger for this LED. A trigger is a kernel based source 51 scheduler is chosen. Trigger specific parameters can appear in 52 /sys/class/leds/<led> once a given trigger is selected. For 53 their documentation see sysfs-class-led-trigger-*. 61 gpio and backlight triggers. In case of the backlight trigger,
|
| D | sysfs-bus-iio-timer-stm32 | 7 used as trigger output (TRGO). 9 as trigger output. 10 - "update" : The update event is selected as trigger output. 13 - "compare_pulse" : The trigger output send a positive pulse 15 - "OC1REF" : OC1REF signal is used as trigger output. 16 - "OC2REF" : OC2REF signal is used as trigger output. 17 - "OC3REF" : OC3REF signal is used as trigger output. 18 - "OC4REF" : OC4REF signal is used as trigger output. 20 - "OC5REF" : OC5REF signal is used as trigger output. 21 - "OC6REF" : OC6REF signal is used as trigger output. [all …]
|
| D | sysfs-bus-iio-adc-stm32 | 5 The STM32 ADC can be configured to use external trigger sources 7 conversions on external trigger by either: 11 Reading returns current trigger polarity. 12 Writing value before enabling conversions sets trigger polarity.
|
| D | sysfs-class-led-trigger-usbport | 8 selected for the USB port trigger. Selecting ports makes trigger
|
| /Documentation/leds/ |
| D | ledtrig-oneshot.rst | 2 One-shot LED Trigger 5 This is a LED trigger useful for signaling the user of an event where there are 7 trigger, the application needs only to signal the trigger when an event has 8 happened, than the trigger turns the LED on and than keeps it off for a 11 This trigger is meant to be usable both for sporadic and dense events. In the 12 first case, the trigger produces a clear single controlled blink for each 20 The trigger can be activated from user space on led class devices as shown 23 echo oneshot > trigger 26 Documentation/ABI/testing/sysfs-class-led-trigger-oneshot 30 echo oneshot > trigger # set trigger for this led
|
| 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 26 Transient trigger addresses the need for one shot timer activation. The 27 transient trigger can be enabled and disabled just like the other leds 31 triggers it supports and a default trigger. During registration, activation 32 routine for the default trigger gets called. During registration of an led 36 trigger will be called, and LED state is changed to LED_OFF. 40 suspend and resume actions and the currently enabled trigger. LED state [all …]
|
| D | ledtrig-usbport.rst | 2 USB port LED trigger 5 This LED trigger can be used for signalling to the user a presence of USB device 13 Please note that this trigger allows selecting multiple USB ports for a single 32 This trigger can be activated from user space on led class devices as shown 35 echo usbport > trigger 38 Documentation/ABI/testing/sysfs-class-led-trigger-usbport 42 echo usbport > trigger
|
| D | leds-class.rst | 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 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. 28 is chosen (via /sys/class/leds/<device>/trigger). Trigger specific 29 parameters can appear in /sys/class/leds/<device> once a given trigger is 148 the LED_BRIGHT_HW_CHANGED flag is a bug and will trigger a WARN_ON. 176 The LED Trigger core cannot be a module as the simple trigger functions [all …]
|
| D | leds-blinkm.rst | 27 brightness device max_brightness power subsystem trigger uevent 30 brightness device max_brightness power subsystem trigger uevent 33 brightness device max_brightness power subsystem trigger uevent 49 $ echo heartbeat > blinkm-6-9-green/trigger
|
| /Documentation/iio/ |
| D | iio_configfs.rst | 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. 76 Each trigger type has its own directory under /config/iio/triggers. Loading 77 iio-trig-sample module will create 'trig-sample' trigger type directory 80 We support the following interrupt sources (trigger types): 87 Loading iio-trig-hrtimer module will register hrtimer trigger types allowing 95 Each trigger can have one or more attributes specific to the trigger type. [all …]
|
| /Documentation/devicetree/bindings/iio/timer/ |
| D | stm32-lptimer-trigger.txt | 1 STMicroelectronics STM32 Low-Power Timer Trigger 3 STM32 Low-Power Timer provides trigger source (LPTIM output) that can be used 10 - compatible: Must be "st,stm32-lptimer-trigger". 11 - reg: Identify trigger hardware block. Must be 0, 1 or 2 13 trigger output. 19 trigger@0 { 20 compatible = "st,stm32-lptimer-trigger";
|
| D | stm32-timer-trigger.txt | 8 "st,stm32-timer-trigger" 9 "st,stm32h7-timer-trigger" 10 - reg: Identify trigger hardware block. 22 compatible = "st,stm32-timer-trigger";
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | ltc2952-poweroff.txt | 3 This chip is used to externally trigger a system shut down. Once the trigger has 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 26 trigger-gpios = <&gpio0 1 GPIO_ACTIVE_LOW>;
|
| /Documentation/trace/ |
| D | events.rst | 312 Trace events can be made to conditionally invoke trigger 'commands' 316 with attached triggers is invoked, the set of trigger commands 317 associated with that event is invoked. Any given trigger can 321 If no filter is associated with the trigger, it always passes. 324 trigger expressions to the 'trigger' file for the given event. 347 /sys/kernel/tracing/events/ftrace/print/trigger 352 Triggers are added by echoing the command to the 'trigger' file:: 354 # echo 'command[:count] [if filter]' > trigger 357 to the 'trigger' file:: 359 # echo '!command[:count] [if filter]' > trigger [all …]
|
| D | histogram.rst | 15 2. Histogram Trigger Command 18 A histogram trigger command is an event trigger command that 24 The format of a hist trigger is as follows:: 50 key. If a hist trigger is given a name using the 'name' parameter, 52 name, and trigger hits will update this common data. Only triggers 54 'compatible' if the fields named in the trigger share the same 63 attached to an event, there will be a table for each trigger in the 64 output. The table displayed for a named trigger will be the same as 99 trigger, read its current contents, and then turn it off:: 102 /sys/kernel/debug/tracing/events/net/netif_rx/trigger [all …]
|
| /Documentation/devicetree/bindings/leds/ |
| D | common.txt | 45 - linux,default-trigger : This parameter, if present, is a 46 string defining the trigger assigned to the LED. Current triggers are: 60 Each trigger may parse this property differently: 66 Documentation/devicetree/bindings/leds/leds-trigger-pattern.txt 80 - trigger-sources : List of devices which should be used as a source triggering 94 #trigger-source-cells property in the source node. 106 * Trigger source providers 108 Each trigger source should be represented by a device tree node. It may be e.g. 111 Required properties for trigger source: 112 - #trigger-source-cells : Number of cells in a source trigger. Typically 0 for [all …]
|
| D | pca963x.txt | 21 - linux,default-trigger : (optional) 35 linux,default-trigger = "none"; 40 linux,default-trigger = "none"; 45 linux,default-trigger = "none"; 50 linux,default-trigger = "none";
|
| D | register-bit-led.txt | 24 - linux,default-trigger : (optional) 40 linux,default-trigger = "heartbeat"; 48 linux,default-trigger = "mmc0"; 56 linux,default-trigger = "cpu0";
|
| /Documentation/devicetree/bindings/mfd/ |
| D | stm32-lptimer.txt | 7 - Trigger source for STM32 ADC/DAC (LPTIM_OUT) 20 - trigger: See ../iio/timer/stm32-lptimer-trigger.txt 38 trigger@0 { 39 compatible = "st,stm32-lptimer-trigger";
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | img,meta-intc.txt | 1 * Meta External Trigger Controller Binding 4 representation of a Meta external trigger controller. 44 * Meta external trigger block 64 // Compatible with Meta hardware trigger block. 72 * trigger block.
|
| /Documentation/accounting/ |
| D | psi.rst | 72 A trigger describes the maximum cumulative stall time over a specific 76 To register a trigger user has to open psi interface file under 79 used to wait for trigger events using select(), poll() or epoll(). 89 Triggers can be set on more than one psi metric and more than one trigger 90 for the same psi metric can be specified. However for each trigger a separate 92 therefore for each trigger a separate open() syscall should be made even 112 The trigger will de-register when the file descriptor used to define the 113 trigger is closed.
|
| /Documentation/input/ |
| D | gamepad.rst | 84 fashion. For example, the "Nintendo Wii Nunchuk" provides two trigger buttons 86 analog stick and two trigger buttons on the right side. 159 Trigger buttons can be available as digital or analog buttons or both. User- 163 Upper trigger buttons are reported as BTN_TR or ABS_HAT1X (right) and BTN_TL 164 or ABS_HAT1Y (left). Lower trigger buttons are reported as BTN_TR2 or 167 If only one trigger-button combination is present (upper+lower), they are 170 (ABS trigger values start at 0, pressure is reported as positive values)
|
12345678910>>...14