| /kernel/linux/linux-5.10/tools/testing/selftests/ftrace/test.d/trigger/ |
| D | trigger-filter.tc | 3 # description: event trigger - test trigger filter
4 # requires: set_event events/sched/sched_process_fork/trigger
12 echo "Test trigger filter"
14 echo 'traceoff if child_pid == 0' > events/sched/sched_process_fork/trigger
17 fail "traceoff trigger on sched_process_fork did not work"
22 echo "Test semantic error for trigger filter"
23 ! echo 'traceoff if a' > events/sched/sched_process_fork/trigger
24 ! echo 'traceoff if common_pid=0' > events/sched/sched_process_fork/trigger
25 ! echo 'traceoff if common_pid==b' > events/sched/sched_process_fork/trigger
26 echo 'traceoff if common_pid == 0' > events/sched/sched_process_fork/trigger
[all …]
|
| D | trigger-eventonoff.tc | 3 # description: event trigger - test event enable/disable trigger
4 # requires: set_event events/sched/sched_process_fork/trigger
12 FEATURE=`grep enable_event events/sched/sched_process_fork/trigger`
14 echo "event enable/disable trigger is not supported"
18 echo "Test enable_event trigger"
20 echo 'enable_event:sched:sched_switch' > events/sched/sched_process_fork/trigger
23 fail "enable_event trigger on sched_process_fork did not work"
28 echo "Test disable_event trigger"
30 echo 'disable_event:sched:sched_switch' > events/sched/sched_process_fork/trigger
33 fail "disable_event trigger on sched_process_fork did not work"
[all …]
|
| D | trigger-traceonoff.tc | 3 # description: event trigger - test traceon/off trigger
4 # requires: set_event events/sched/sched_process_fork/trigger
11 echo "Test traceoff trigger"
13 echo 'traceoff' > events/sched/sched_process_fork/trigger
16 fail "traceoff trigger on sched_process_fork did not work"
21 echo "Test traceon trigger"
23 echo 'traceon' > events/sched/sched_process_fork/trigger
26 fail "traceoff trigger on sched_process_fork did not work"
31 echo "Test semantic error for traceoff/on trigger"
32 ! echo 'traceoff:badparam' > events/sched/sched_process_fork/trigger
[all …]
|
| D | trigger-stacktrace.tc | 3 # description: event trigger - test stacktrace-trigger
4 # requires: set_event events/sched/sched_process_fork/trigger
11 FEATURE=`grep stacktrace events/sched/sched_process_fork/trigger`
13 echo "stacktrace trigger is not supported"
17 echo "Test stacktrace trigger"
20 echo 'stacktrace' > events/sched/sched_process_fork/trigger
23 fail "stacktrace trigger on sched_process_fork did not work"
29 ! echo "stacktrace:foo" > events/sched/sched_process_fork/trigger
30 echo "stacktrace" > events/sched/sched_process_fork/trigger
31 ! echo "stacktrace" > events/sched/sched_process_fork/trigger
|
| D | trigger-snapshot.tc | 3 # description: event trigger - test snapshot-trigger
4 # requires: set_event events/sched/sched_process_fork/trigger snapshot
11 FEATURE=`grep snapshot events/sched/sched_process_fork/trigger`
13 echo "snapshot trigger is not supported"
17 echo "Test snapshot trigger"
21 echo 'snapshot:1' > events/sched/sched_process_fork/trigger
24 fail "snapshot trigger on sched_process_fork did not work"
32 ! echo "snapshot+1" > events/sched/sched_process_fork/trigger
33 echo "snapshot" > events/sched/sched_process_fork/trigger
34 ! echo "snapshot" > events/sched/sched_process_fork/trigger
|
| /kernel/linux/linux-4.19/tools/testing/selftests/ftrace/test.d/trigger/ |
| D | trigger-filter.tc | 3 # description: event trigger - test trigger filter
23 if [ ! -f events/sched/sched_process_fork/trigger ]; then
24 echo "event trigger is not supported"
31 echo "Test trigger filter"
33 echo 'traceoff if child_pid == 0' > events/sched/sched_process_fork/trigger
36 fail "traceoff trigger on sched_process_fork did not work"
41 echo "Test semantic error for trigger filter"
42 ! echo 'traceoff if a' > events/sched/sched_process_fork/trigger
43 ! echo 'traceoff if common_pid=0' > events/sched/sched_process_fork/trigger
44 ! echo 'traceoff if common_pid==b' > events/sched/sched_process_fork/trigger
[all …]
|
| D | trigger-eventonoff.tc | 3 # description: event trigger - test event enable/disable trigger
23 if [ ! -f events/sched/sched_process_fork/trigger ]; then
24 echo "event trigger is not supported"
31 FEATURE=`grep enable_event events/sched/sched_process_fork/trigger`
33 echo "event enable/disable trigger is not supported"
37 echo "Test enable_event trigger"
39 echo 'enable_event:sched:sched_switch' > events/sched/sched_process_fork/trigger
42 fail "enable_event trigger on sched_process_fork did not work"
47 echo "Test disable_event trigger"
49 echo 'disable_event:sched:sched_switch' > events/sched/sched_process_fork/trigger
[all …]
|
| D | trigger-traceonoff.tc | 3 # description: event trigger - test traceon/off trigger
22 if [ ! -f events/sched/sched_process_fork/trigger ]; then
23 echo "event trigger is not supported"
30 echo "Test traceoff trigger"
32 echo 'traceoff' > events/sched/sched_process_fork/trigger
35 fail "traceoff trigger on sched_process_fork did not work"
40 echo "Test traceon trigger"
42 echo 'traceon' > events/sched/sched_process_fork/trigger
45 fail "traceoff trigger on sched_process_fork did not work"
50 echo "Test semantic error for traceoff/on trigger"
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/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 …]
|
| /kernel/linux/linux-4.19/Documentation/leds/ |
| D | ledtrig-transient.txt | 1 LED Transient Trigger
4 The leds timer trigger does not currently have an interface to activate
9 should stay in off state. The on and off cycle repeats until the trigger
14 Without one shot timer interface, user space can still use timer trigger to
25 Transient trigger addresses the need for one shot timer activation. The
26 transient trigger can be enabled and disabled just like the other leds
30 triggers it supports and a default trigger. During registration, activation
31 routine for the default trigger gets called. During registration of an led
35 trigger will be called, and LED state is changed to LED_OFF.
39 suspend and resume actions and the currently enabled trigger. LED state
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/drivers/leds/trigger/ |
| D | Kconfig | 3 bool "LED Trigger support"
6 This option enables trigger support for the leds class.
13 tristate "LED Timer Trigger"
23 tristate "LED One-shot Trigger"
36 bool "LED Disk Trigger"
43 bool "LED MTD (NAND/NOR) Trigger"
50 tristate "LED Heartbeat Trigger"
58 tristate "LED backlight Trigger"
66 bool "LED CPU Trigger"
75 tristate "LED activity Trigger"
[all …]
|
| /kernel/linux/linux-4.19/include/linux/iio/ |
| D | trigger.h | 1 /* The industrial I/O core, trigger handling functions
26 * @set_trigger_state: switch on/off the trigger on demand
27 * @try_reenable: function to reenable the trigger when the
30 * current trigger gets changed.
44 * struct iio_trigger - industrial I/O trigger device
50 * @list: [INTERN] used in maintenance of global trigger list
51 * @alloc_list: [DRIVER] used for driver specific trigger list
52 * @use_count: [INTERN] use count for the trigger.
54 * @subirq_base: [INTERN] base number for irqs provided by trigger.
58 * @attached_own_device:[INTERN] if we are using our own device as trigger,
[all …]
|
| /kernel/linux/linux-5.10/include/linux/iio/ |
| D | trigger.h | 2 /* The industrial I/O core, trigger handling functions
23 * @set_trigger_state: switch on/off the trigger on demand
24 * @try_reenable: function to reenable the trigger when the
27 * current trigger gets changed.
41 * struct iio_trigger - industrial I/O trigger device
47 * @list: [INTERN] used in maintenance of global trigger list
48 * @alloc_list: [DRIVER] used for driver specific trigger list
49 * @use_count: [INTERN] use count for the trigger.
51 * @subirq_base: [INTERN] base number for irqs provided by trigger.
55 * @attached_own_device:[INTERN] if we are using our own device as trigger,
[all …]
|
| /kernel/linux/linux-4.19/drivers/leds/trigger/ |
| D | Kconfig | 2 bool "LED Trigger support"
5 This option enables trigger support for the leds class.
12 tristate "LED Timer Trigger"
22 tristate "LED One-shot Trigger"
35 bool "LED Disk Trigger"
42 bool "LED MTD (NAND/NOR) Trigger"
49 tristate "LED Heartbeat Trigger"
57 tristate "LED backlight Trigger"
65 bool "LED CPU Trigger"
74 tristate "LED activity Trigger"
[all …]
|
| /kernel/linux/linux-4.19/drivers/iio/trigger/ |
| D | Kconfig | 9 tristate "High resolution timer trigger"
12 Provides a frequency based IIO trigger using high resolution
19 tristate "Generic interrupt trigger"
22 trigger. This may be provided by a gpio driver for example.
28 tristate "STM32 Low-Power Timer Trigger"
31 Select this option to enable STM32 Low-Power Timer Trigger.
32 This can be used as trigger source for STM32 internal ADC
36 module will be called stm32-lptimer-trigger.
39 tristate "STM32 Timer Trigger"
42 Select this option to enable STM32 Timer Trigger
[all …]
|
| /kernel/linux/linux-5.10/drivers/iio/trigger/ |
| D | Kconfig | 10 tristate "High resolution timer trigger"
13 Provides a frequency based IIO trigger using high resolution
20 tristate "Generic interrupt trigger"
23 trigger. This may be provided by a gpio driver for example.
29 tristate "STM32 Low-Power Timer Trigger"
32 Select this option to enable STM32 Low-Power Timer Trigger.
33 This can be used as trigger source for STM32 internal ADC
37 module will be called stm32-lptimer-trigger.
40 tristate "STM32 Timer Trigger"
43 Select this option to enable STM32 Timer Trigger
[all …]
|
| /kernel/linux/linux-4.19/tools/perf/util/ |
| D | trigger.h | 9 * Use trigger to model operations which need to be executed when
22 * a trigger. is_hit means the event already happen; is_ready means the
23 * trigger is waiting for the event.
26 struct trigger { struct
38 WARN_ONCE(t->state != exp, "trigger '%s' state transist error: %d in %s()\n", \ argument
41 static inline bool trigger_is_available(struct trigger *t) in trigger_is_available()
46 static inline bool trigger_is_error(struct trigger *t) in trigger_is_error()
51 static inline void trigger_on(struct trigger *t) in trigger_on()
57 static inline void trigger_ready(struct trigger *t) in trigger_ready()
64 static inline void trigger_hit(struct trigger *t) in trigger_hit()
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/util/ |
| D | trigger.h | 8 * Use trigger to model operations which need to be executed when
21 * a trigger. is_hit means the event already happen; is_ready means the
22 * trigger is waiting for the event.
25 struct trigger { struct
37 WARN_ONCE(t->state != exp, "trigger '%s' state transist error: %d in %s()\n", \ argument
40 static inline bool trigger_is_available(struct trigger *t) in trigger_is_available()
45 static inline bool trigger_is_error(struct trigger *t) in trigger_is_error()
50 static inline void trigger_on(struct trigger *t) in trigger_on()
56 static inline void trigger_ready(struct trigger *t) in trigger_ready()
63 static inline void trigger_hit(struct trigger *t) in trigger_hit()
[all …]
|
| /kernel/linux/linux-4.19/kernel/trace/ |
| D | trace_events_trigger.c | 35 * For each trigger associated with an event, invoke the trigger
36 * function registered with the associated trigger command. If rec is
37 * non-NULL, it means that the trigger requires further processing and
39 * trigger has a filter associated with it, rec will checked against
40 * the filter and if the record matches the trigger will be invoked.
41 * If the trigger is a 'post_trigger', meaning it shouldn't be invoked
42 * in any case until the current event is written, the trigger
44 * trigger is set in the return value.
47 * any trigger that should be deferred, ETT_NONE if nothing to defer.
52 * any trigger that should be deferred, ETT_NONE if nothing to defer.
[all …]
|
| /kernel/linux/linux-5.10/kernel/trace/ |
| D | trace_events_trigger.c | 36 * For each trigger associated with an event, invoke the trigger
37 * function registered with the associated trigger command. If rec is
38 * non-NULL, it means that the trigger requires further processing and
40 * trigger has a filter associated with it, rec will checked against
41 * the filter and if the record matches the trigger will be invoked.
42 * If the trigger is a 'post_trigger', meaning it shouldn't be invoked
43 * in any case until the current event is written, the trigger
45 * trigger is set in the return value.
48 * any trigger that should be deferred, ETT_NONE if nothing to defer.
53 * any trigger that should be deferred, ETT_NONE if nothing to defer.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/iio/ |
| D | iio_configfs.txt | 33 trigger types. A new trigger type is usually implemented as a separate
37 * drivers/iio/trigger/iio-trig-sample.c
38 * sample kernel module implementing a new trigger type
46 * This allocates and registers an IIO trigger plus other
47 * trigger type specific initialization.
71 Each trigger type has its own directory under /config/iio/triggers. Loading
72 iio-trig-sample module will create 'trig-sample' trigger type directory
75 We support the following interrupt sources (trigger types):
80 Loading iio-trig-hrtimer module will register hrtimer trigger types allowing
88 Each trigger can have one or more attributes specific to the trigger type.
[all …]
|