| /kernel/linux/linux-4.19/Documentation/iio/ |
| D | iio_configfs.txt | 7 triggers).
26 3. Software triggers
28 One of the IIO default configfs groups is the "triggers" group. It is
30 under /config/iio/triggers.
32 IIO software triggers implementation offers support for creating multiple
71 Each trigger type has its own directory under /config/iio/triggers. Loading
73 /config/iio/triggers/trig-sample.
78 3.1 Hrtimer triggers creation and destruction
81 users to create hrtimer triggers under /config/iio/triggers/hrtimer.
85 $ mkdir /config/iio/triggers/hrtimer/instance1
[all …]
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-4.19/drivers/staging/iio/Documentation/ |
| D | trigger.txt | 3 Many triggers are provided by hardware that will also be registered as
5 such triggers are registered with the core in the same way as
6 stand-alone triggers.
18 triggers to keep track of what they have created.
29 Currently triggers are only used for the filling of software
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-4.19/kernel/trace/ |
| D | trace_events_trigger.c | 3 * trace_events_trigger - trace event triggers
24 /* make sure current triggers exit before free */ in trigger_data_free()
31 * event_triggers_call - Call triggers associated with a trace event
62 if (list_empty(&file->triggers)) in event_triggers_call()
65 list_for_each_entry_rcu(data, &file->triggers, list) { in event_triggers_call()
103 list_for_each_entry_rcu(data, &file->triggers, list) { in event_triggers_post_call()
122 return seq_list_next(t, &event_file->triggers, pos); in trigger_next()
135 if (list_empty(&event_file->triggers)) in trigger_start()
138 return seq_list_start(&event_file->triggers, *pos); in trigger_start()
152 seq_puts(m, "# Available triggers:\n"); in trigger_show()
[all …]
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-4.19/include/linux/platform_data/ |
| D | at91_adc.h | 17 * struct at91_adc_trigger - description of triggers
33 * @trigger_list: Triggers available in the ADC
34 * @trigger_number: Number of triggers available in the ADC
35 * @use_external_triggers: does the board has external triggers availables
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-5.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
|
| /kernel/linux/linux-4.19/tools/testing/selftests/ftrace/test.d/ftrace/ |
| D | func_traceonoff_triggers.tc | 3 # description: ftrace - test for function traceon/off triggers
6 # Ftrace allows to add triggers to functions, such as enabling or disabling
10 # This test is designed to test enabling and disabling tracing triggers
13 # The triggers are set within the set_ftrace_filter file
181 fail "Tracing on and off triggers still exist"
|
| D | func_event_triggers.tc | 3 # description: ftrace - test for function event triggers
6 # Ftrace allows to add triggers to functions, such as enabling or disabling
10 # This test is designed to test event triggers
13 # The triggers are set within the set_ftrace_filter file
|
| /kernel/linux/linux-4.19/Documentation/leds/ |
| D | leds-class.txt | 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 whilst available to all LEDs have LED specific
27 You can change triggers in a similar manner to the way an IO scheduler
120 particular LED (ACPI?). The addition of triggers provided by the LED driver
|
| /kernel/linux/linux-4.19/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()
|
| /kernel/linux/linux-5.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()
|
| /kernel/linux/linux-4.19/Documentation/trace/ |
| D | events.rst | 309 6. Event triggers
316 with attached triggers is invoked, the set of trigger commands
323 Triggers are added to and removed from a particular event by writing
326 A given event can have any number of triggers associated with it,
330 Event triggers are implemented on top of "soft" mode, which means that
331 whenever a trace event has one or more triggers associated with it,
335 This scheme allows triggers to be invoked even for events that aren't
337 used for conditionally invoking triggers.
339 The syntax for event triggers is roughly based on the syntax for
346 can also enable triggers that are written into
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | configfs-iio | 10 What: /config/iio/triggers
14 Industrial IO software triggers directory.
16 What: /config/iio/triggers/hrtimers
|
| /kernel/linux/linux-4.19/tools/testing/selftests/ftrace/test.d/ |
| D | functions | 19 # remove action triggers first
34 reset_trigger() { # reset all current setting triggers
48 reset_ftrace_filter() { # reset all triggers in set_ftrace_filter
86 # no events, no triggers, no filters, no function filters,
|
| /kernel/linux/linux-5.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,
|
| /kernel/linux/linux-5.10/Documentation/driver-api/iio/ |
| D | triggers.rst | 2 Triggers title
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
|
| /kernel/linux/linux-4.19/Documentation/driver-api/iio/ |
| D | triggers.rst | 2 Triggers title
26 There are two locations in sysfs related to triggers:
31 Because triggers can be very different depending on type there are few
36 * :file:`sampling_frequency`, some timer based triggers use this attribute to
|