Searched full:trigger (Results 1 – 25 of 376) sorted by relevance
12345678910>>...16
| /Documentation/driver-api/iio/ |
| D | triggers.rst | 5 * struct iio_trigger — industrial I/O trigger device
9 * :c:func:`iio_trigger_validate_own_device` — Check if a trigger and IIO
13 on some external event (trigger) as opposed to periodically polling for data.
14 An IIO trigger can be provided by a device driver that also has an IIO device
18 a specific file in sysfs). A trigger may initiate data capture for a number of
21 IIO trigger sysfs interface
26 * :file:`/sys/bus/iio/devices/trigger{Y}/*`, this file is created once an
27 IIO trigger is registered with the IIO core and corresponds to trigger
32 * :file:`name`, trigger name that can be later used for association with a
35 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/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 …]
|
| 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-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 …]
|
| /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 | 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.
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
73 their documentation see `sysfs-class-led-trigger-*`.
81 gpio and backlight triggers. In case of the backlight trigger,
|
| D | sysfs-bus-iio-timer-stm32 | 10 used as trigger output (TRGO).
13 as trigger output.
15 The update event is selected as trigger output.
19 The trigger output send a positive pulse
22 OC1REF signal is used as trigger output.
24 OC2REF signal is used as trigger output.
26 OC3REF signal is used as trigger output.
28 OC4REF signal is used as trigger output.
33 OC5REF signal is used as trigger output.
35 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:
13 Reading returns current trigger polarity.
15 Writing value before enabling conversions sets trigger polarity.
|
| D | sysfs-bus-coresight-devices-cti | 35 Description: (Read) Input trigger signals from connected device <N>
41 Description: (Read) Functional types for the input trigger signals
48 Description: (Read) Output trigger signals to connected device <N>
54 Description: (Read) Functional types for the output trigger signals
129 Description: (Read) read current status of input trigger signals
135 Description: (Read) read current status of output trigger signals.
141 Description: (Write) Attach a CTI input trigger to a CTM channel.
147 Description: (Write) Detach a CTI input trigger from a CTM channel.
153 Description: (Write) Attach a CTI output trigger to a CTM channel.
159 Description: (Write) Detach a CTI output trigger from a CTM channel.
[all …]
|
| D | sysfs-class-led-trigger-usbport | 8 selected for the USB port trigger. Selecting ports makes 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/leds/ |
| D | trigger-source.yaml | 4 $id: http://devicetree.org/schemas/leds/trigger-source.yaml#
7 title: Trigger source providers
14 Each trigger source provider should be represented by a device tree node. It
18 '#trigger-source-cells':
20 Number of cells in a source trigger. Typically 0 for nodes of simple
21 trigger sources (e.g. a specific USB port).
|
| 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 | common.yaml | 76 linux,default-trigger:
78 This parameter, if present, is a string defining the trigger assigned to
105 Each trigger may parse this property differently:
111 Documentation/devicetree/bindings/leds/leds-trigger-pattern.txt
131 trigger-sources:
145 #trigger-source-cells property in the source node.
171 linux,default-trigger = "heartbeat";
178 trigger-sources = <&ohci_port1>, <&ehci_port1>;
208 linux,default-trigger = "heartbeat";
|
| 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/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/coresight/ |
| D | coresight-ect.rst | 4 CoreSight Embedded Cross Trigger (CTI & CTM).
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
31 channels. When an input trigger becomes active, the attached channel will
32 become active. Any output trigger attached to that channel will also
43 no programmed trigger/channel attachments, so will not affect the system
46 The hardware trigger connections between CTIs and devices is implementation
50 The hardware trigger signals can also be connected to non-CoreSight devices
72 capable of generating or using trigger signals.::
100 Individual trigger connection information. This describes trigger signals for
[all …]
|
| /Documentation/trace/ |
| 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 …]
|
| D | events.rst | 331 Trace events can be made to conditionally invoke trigger 'commands'
335 with attached triggers is invoked, the set of trigger commands
336 associated with that event is invoked. Any given trigger can
340 If no filter is associated with the trigger, it always passes.
343 trigger expressions to the 'trigger' file for the given event.
367 /sys/kernel/tracing/events/ftrace/print/trigger
372 Triggers are added by echoing the command to the 'trigger' file::
374 # echo 'command[:count] [if filter]' > trigger
377 to the 'trigger' file::
379 # echo '!command[:count] [if filter]' > trigger
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | coresight-cti.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
40 When CTI trigger connection information is unavailable then a minimal driver
41 binding can be declared with no explicit trigger signals. This will result
48 configuration). These registers may be used to explore the trigger connections
60 Note that some hardware trigger signals can be connected to non-CoreSight
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | st,stm32-lptimer.yaml | 13 - Trigger source for STM32 ADC/DAC (LPTIM_OUT)
62 "^trigger@[0-9]+$":
67 const: st,stm32-lptimer-trigger
70 description: Identify trigger hardware block.
127 trigger@0 {
128 compatible = "st,stm32-lptimer-trigger";
|
| /Documentation/accounting/ |
| D | psi.rst | 74 A trigger describes the maximum cumulative stall time over a specific
78 To register a trigger user has to open psi interface file under
81 used to wait for trigger events using select(), poll() or epoll().
91 Triggers can be set on more than one psi metric and more than one trigger
92 for the same psi metric can be specified. However for each trigger a separate
94 therefore for each trigger a separate open() syscall should be made even
96 with an already existing psi trigger will fail with EBUSY.
115 The trigger will de-register when the file descriptor used to define the
116 trigger is closed.
|
| /Documentation/fault-injection/ |
| D | provoke-crashes.rst | 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
30 Where in the kernel to trigger the action. It can be
|
12345678910>>...16