| /Linux-v5.10/Documentation/iio/ |
| D | iio_configfs.rst | 10 triggers).
30 3. Software triggers
33 One of the IIO default configfs groups is the "triggers" group. It is
35 under /config/iio/triggers.
37 IIO software triggers implementation offers support for creating multiple
76 Each trigger type has its own directory under /config/iio/triggers. Loading
78 /config/iio/triggers/trig-sample.
84 3.1 Hrtimer triggers creation and destruction
88 users to create hrtimer triggers under /config/iio/triggers/hrtimer.
92 $ mkdir /config/iio/triggers/hrtimer/instance1
[all …]
|
| /Linux-v5.10/Documentation/trace/coresight/ |
| D | coresight-ect.rst | 14 individual input and output hardware signals known as triggers to and from
30 The CTI driver enables the programming of the CTI to attach triggers to
34 activating connected output triggers there, unless filtered by the CTI
84 * ``nr_trigger_cons`` : total connections - triggers<N> directories.
88 * ``triggers<N>``: contains list of triggers for an individual connection.
97 triggers<N> directories
103 Each triggers directory has a set of parameters describing the triggers for
127 If a connection has zero signals in either the 'in' or 'out' triggers then
133 This provides an easy way to attach triggers to channels, without needing
180 * ``chan_xtrigs_in``: Read to show the input triggers attached to
[all …]
|
| /Linux-v5.10/kernel/trace/ |
| D | trace_events_trigger.c | 3 * trace_events_trigger - trace event triggers
25 /* make sure current triggers exit before free */ in trigger_data_free()
32 * event_triggers_call - Call triggers associated with a trace event
63 if (list_empty(&file->triggers)) in event_triggers_call()
66 list_for_each_entry_rcu(data, &file->triggers, list) { in event_triggers_call()
104 list_for_each_entry_rcu(data, &file->triggers, list) { in event_triggers_post_call()
123 return seq_list_next(t, &event_file->triggers, pos); in trigger_next()
136 if (list_empty(&event_file->triggers)) in trigger_start()
139 return seq_list_start(&event_file->triggers, *pos); in trigger_start()
153 seq_puts(m, "# Available triggers:\n"); in trigger_show()
[all …]
|
| /Linux-v5.10/drivers/iio/ |
| D | Kconfig | 30 (e.g. software triggers). For more info see
36 Provides IIO core support for triggers. Currently these
38 buffers. The triggers are effectively a 'capture
58 tristate "Enable software triggers support"
61 Provides IIO core support for software triggers. A software
|
| /Linux-v5.10/include/linux/platform_data/ |
| D | at91_adc.h | 16 * struct at91_adc_trigger - description of triggers
32 * @trigger_list: Triggers available in the ADC
33 * @trigger_number: Number of triggers available in the ADC
34 * @use_external_triggers: does the board has external triggers availables
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-coresight-devices-cti | 23 Description: (Read) Number of devices connected to triggers on this CTI
25 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/name
31 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_signals
37 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_types
44 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/out_signals
50 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/out_types
196 Description: (Read) List of output triggers filtered across all connections.
227 Description: (Read) Read to see input triggers connected to selected view
234 Description: (Read) Read to see output triggers connected to selected view
|
| D | configfs-iio | 10 What: /config/iio/triggers
14 Industrial IO software triggers directory.
16 What: /config/iio/triggers/hrtimers
|
| D | sysfs-platform-dell-laptop | 27 This file allows to control the input triggers that
30 Read the file to see the triggers available. The ones
45 Note that not all the available triggers can be configured.
|
| /Linux-v5.10/tools/testing/selftests/ftrace/test.d/ftrace/ |
| D | func_traceonoff_triggers.tc | 3 # description: ftrace - test for function traceon/off triggers
6 # The triggers are set within the set_ftrace_filter file
9 # Ftrace allows to add triggers to functions, such as enabling or disabling
13 # This test is designed to test enabling and disabling tracing triggers
167 fail "Tracing on and off triggers still exist"
|
| D | func_event_triggers.tc | 3 # description: ftrace - test for function event triggers
6 # The triggers are set within the set_ftrace_filter file
9 # Ftrace allows to add triggers to functions, such as enabling or disabling
13 # This test is designed to test event triggers
|
| /Linux-v5.10/drivers/net/wireless/ath/ath9k/ |
| D | wow.c | 173 u8 triggers; in ath9k_suspend() local
187 ath_err(common, "None of the WoW triggers enabled\n"); in ath9k_suspend()
213 triggers = ath9k_wow_map_triggers(sc, wowlan); in ath9k_suspend()
214 if (!triggers) { in ath9k_suspend()
215 ath_dbg(common, WOW, "No valid WoW triggers\n"); in ath9k_suspend()
238 if (triggers & AH_WOW_USER_PATTERN_EN) { in ath9k_suspend()
269 ath9k_hw_wow_enable(ah, triggers); in ath9k_suspend()
272 ath_dbg(common, WOW, "Suspend with WoW triggers: 0x%x\n", triggers); in ath9k_suspend()
|
| /Linux-v5.10/Documentation/driver-api/iio/ |
| D | triggers.rst | 2 Triggers chapter
24 There are two locations in sysfs related to triggers:
29 Because triggers can be very different depending on type there are few
34 * :file:`sampling_frequency`, some timer based triggers use this attribute to
|
| /Linux-v5.10/tools/bootconfig/scripts/ |
| D | ftrace.sh | 20 # remove action triggers first
35 reset_trigger() { # reset all current setting triggers
49 reset_ftrace_filter() { # reset all triggers in set_ftrace_filter
90 # no events, no triggers, no filters, no function filters,
|
| /Linux-v5.10/Documentation/input/ |
| D | gamepad.rst | 20 / [__ TL __] [__ TR __] \ | Front Triggers
58 - Triggers
59 Triggers are located on the upper-side of the pad in vertical direction.
61 Left- and Right-Triggers, the lower buttons Z-Left and Z-Right.
157 - Triggers:
168 reported as "right" triggers (BTN_TR/ABS_HAT1X).
|
| /Linux-v5.10/Documentation/devicetree/bindings/dma/ |
| D | st,stm32-mdma.yaml | 43 0x00: Each MDMA request triggers a buffer transfer (max 128 bytes)
44 0x1: Each MDMA request triggers a block transfer (max 64K bytes)
45 0x2: Each MDMA request triggers a repeated block transfer
46 0x3: Each MDMA request triggers a linked list transfer
|
| /Linux-v5.10/Documentation/leds/ |
| D | leds-class.rst | 12 is a kernel based source of led events. Triggers can either be simple or
15 nand-disk and sharpsl-charge triggers. With led triggers disabled, the code
18 Complex triggers while available to all LEDs have LED specific
27 You can change triggers in a similar manner to the way an IO scheduler
187 particular LED (ACPI?). The addition of triggers provided by the LED driver
|
| /Linux-v5.10/drivers/scsi/mpt3sas/ |
| D | mpt3sas_trigger_diag.h | 3 * to set Diagnostic triggers for MPT (Message Passing Technology) based
103 * list of Event Triggers to be monitored for.
108 * This binary structure is transferred via sysfs to get/set Event Triggers
143 * Triggers in the Linux Driver.
172 * This binary structure is transferred via sysfs to get/set MPI Error Triggers
|
| /Linux-v5.10/drivers/iio/trigger/ |
| D | Kconfig | 3 # Industrial I/O standalone triggers
7 menu "Triggers - standalone"
65 Provides support for using SYSFS entries as IIO triggers.
|
| /Linux-v5.10/Documentation/hwmon/ |
| D | w83793.rst | 65 For voltage sensors, an alarm triggers if the measured value is below
67 For temperature sensors, an alarm triggers if the measured value goes
70 For fan sensors, an alarm triggers if the measured value is below the
101 If the case open alarm triggers, it will stay in this state unless cleared
|
| /Linux-v5.10/drivers/power/supply/ |
| D | power_supply_leds.c | 3 * LEDs triggers for power supply class
19 /* Battery specific LEDs triggers. */
111 /* Generated power specific LEDs triggers. */
146 /* Choice what triggers to create&update. */
|
| /Linux-v5.10/kernel/configs/ |
| D | nopm.config | 5 # Triggers PM on OMAP
8 # Triggers enablement via hibernate callbacks
|
| /Linux-v5.10/tools/testing/selftests/ftrace/test.d/ |
| D | functions | 18 # remove action triggers first
33 reset_trigger() { # reset all current setting triggers
47 reset_ftrace_filter() { # reset all triggers in set_ftrace_filter
88 # no events, no triggers, no filters, no function filters,
|
| /Linux-v5.10/include/linux/ |
| D | leds.h | 3 * Driver model for leds and led triggers
149 /* LEDs that have private triggers have this set */
339 * LED Triggers
341 /* Registration functions for simple triggers */
355 /* LED-private triggers have this set */
358 /* LEDs under control by this trigger (for simple triggers) */
377 /* Registration functions for complex triggers */
420 * This is meant to be used on triggers with statically
485 * Generic LED platform data for describing LED names and default triggers.
|
| /Linux-v5.10/drivers/hwtracing/coresight/ |
| D | coresight-cti.h | 55 * CTI CSSoc 400 has 8 IO triggers - other CTIs can be impl def.
124 * @trig_in_use: bitfield of in triggers registered as in use.
125 * @trig_out_use: bitfield of out triggers registered as in use.
126 * @trig_out_filter: bitfield of out triggers that are blocked if filter
148 /* registered triggers and filtering */
|
| /Linux-v5.10/arch/arm/mach-footbridge/ |
| D | ebsa285.c | 33 * The triggers lines up below will only be used if the
34 * LED triggers are compiled in.
107 * Since we may have triggers on any subsystem, defer registration
|
