| /kernel/linux/linux-6.6/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-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-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-6.6/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-6.6/tools/testing/selftests/powerpc/dexcr/ |
| D | dexcr.c | 30 * If the SPR is not recognised by the hardware it triggers in dexcr_exists()
47 * Just test if a bad hashchk triggers a signal, without checking
53 volatile bool triggers; in hashchk_triggers() local
59 triggers = true; in hashchk_triggers()
61 triggers = false; in hashchk_triggers()
65 return triggers; in hashchk_triggers()
115 * If they differ, an interrupt triggers.
|
| /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-6.6/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
66 if (list_empty(&file->triggers)) in event_triggers_call()
69 list_for_each_entry_rcu(data, &file->triggers, list) { in event_triggers_call()
121 list_for_each_entry_rcu(data, &file->triggers, list) { in event_triggers_post_call()
140 return seq_list_next(t, &event_file->triggers, pos); in trigger_next()
147 list_for_each_entry_rcu(data, &file->triggers, list, in check_user_trigger()
166 if (list_empty(&event_file->triggers) || !check_user_trigger(event_file)) in trigger_start()
169 return seq_list_start(&event_file->triggers, *pos); in trigger_start()
[all …]
|
| /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-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-6.6/drivers/iio/ |
| D | Kconfig | 30 (e.g. software triggers). For more info see
39 Provides IIO core support for triggers. Currently these
41 buffers. The triggers are effectively a 'capture
61 tristate "Enable software triggers support"
64 Provides IIO core support for software triggers. A software
|
| /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-6.6/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-6.6/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-6.6/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-6.6/Documentation/translations/zh_CN/iio/ |
| D | iio_configfs.rst | 82 模块将创建“trig-sample”触发器类型目录/config/iio/triggers/trig-sample.
92 /config/iio/triggers/hrtimer下创建hrtimer触发器。
96 $ mkdir /config/iio/triggers/hrtimer/instance1
97 $ rmdir /config/iio/triggers/hrtimer/instance1
|
| /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-6.6/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-6.6/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
|