| /linux/tools/testing/selftests/ftrace/test.d/trigger/ |
| H A 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 …]
|
| H A 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 …]
|
| H A 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 …]
|
| H A D | trigger-hist-expressions.tc | 3 # description: event trigger - test histogram expression parsing
4 # requires: set_event events/sched/sched_process_fork/trigger events/sched/sched_process_fork/hist …
13 trigger="events/sched/sched_process_fork/trigger"
15 reset_trigger_file $trigger
17 echo "Test hist trigger expressions - $1"
19 echo "hist:keys=common_pid:x=$2" > $trigger
23 actual=`grep -o 'x=[[:digit:]]*' $trigger | awk -F= '{ print $2 }'`
26 … fail "Failed hist trigger expression evaluation: Expression: $2 Expected: $3, Actual: $actual"
29 reset_trigger_file $trigger
33 trigger="events/sched/sched_process_fork/trigger"
[all …]
|
| H A 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
|
| H A 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
|
| H A D | trigger-trace-marker-synthetic-kernel.tc | 3 # description: trace_marker trigger - test histogram with synthetic event against kernel event
4 # requires: set_event synthetic_events events/sched/sched_waking events/ftrace/print/trigger events…
12 echo "Test histogram kernel event to trace_marker latency histogram trigger"
15 echo 'hist:keys=pid:ts0=common_timestamp.usecs' > events/sched/sched_waking/trigger
16 …ommon_timestamp.usecs-$ts0:onmatch(sched.sched_waking).latency($lat)' > events/ftrace/print/trigger
17 echo 'hist:keys=common_pid,lat:sort=lat' > events/synthetic/latency/trigger
22 fail "hist trigger did not trigger correct times on trace_marker"
25 fail "hist trigger did not trigger "
|
| H A D | trigger-trace-marker-synthetic.tc | 3 # description: trace_marker trigger - test histogram with synthetic event
4 # requires: set_event synthetic_events events/ftrace/print/trigger events/ftrace/print/hist
12 echo "Test histogram trace_marker to trace_marker latency histogram trigger"
15 …o 'hist:keys=common_pid:ts0=common_timestamp.usecs if buf == "start"' > events/ftrace/print/trigger
16 …tamp.usecs-$ts0:onmatch(ftrace.print).latency($lat) if buf == "end"' >> events/ftrace/print/trigger
17 echo 'hist:keys=common_pid,lat:sort=lat' > events/synthetic/latency/trigger
24 fail "hist trace_marker trigger did not trigger correctly"
28 fail "hist trigger did not trigger "
|
| /linux/Documentation/driver-api/iio/ |
| H A 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 …]
|
| /linux/kernel/trace/ |
| H A D | trace_events_trigger.c | 38 * For each trigger associated with an event, invoke the trigger
39 * function registered with the associated trigger command. If rec is
40 * non-NULL, it means that the trigger requires further processing and
42 * trigger has a filter associated with it, rec will checked against
43 * the filter and if the record matches the trigger will be invoked.
44 * If the trigger is a 'post_trigger', meaning it shouldn't be invoked
45 * in any case until the current event is written, the trigger
47 * trigger is set in the return value.
50 * any trigger that should be deferred, ETT_NONE if nothing to defer.
55 * any trigger that should be deferred, ETT_NONE if nothing to defer.
[all …]
|
| /linux/Documentation/leds/ |
| H A 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 …]
|
| H A 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.
185 unique trigger name supported by the LED in hw control
[all …]
|
| H A 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, then the trigger turns the LED on and then 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
|
| /linux/include/linux/iio/ |
| H A D | trigger.h | 2 /* The industrial I/O core, trigger handling functions
23 * @set_trigger_state: switch on/off the trigger on demand
24 * @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 …]
|
| /linux/drivers/leds/trigger/ |
| H A 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"
76 tristate "LED activity Trigger"
[all …]
|
| H A D | ledtrig-panic.c | 3 * Kernel Panic LED Trigger
15 static struct led_trigger *trigger; variable
19 * notifier. This means the trigger can be changed without
24 if (led_cdev->trigger) in led_trigger_set_panic()
26 list_add_tail(&led_cdev->trig_list, &trigger->led_cdevs); in led_trigger_set_panic()
32 led_cdev->trigger = trigger; in led_trigger_set_panic()
52 led_trigger_event(trigger, state ? LED_FULL : LED_OFF); in led_panic_blink()
58 led_trigger_register_simple("panic", &trigger); in ledtrig_panic_init()
59 if (!trigger) in ledtrig_panic_init()
|
| /linux/drivers/iio/trigger/ |
| H A 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 …]
|
| /linux/tools/perf/util/ |
| H A 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 …]
|
| /linux/tools/tracing/rtla/src/ |
| H A D | trace.c | 214 if (free_event->trigger) in trace_events_free()
215 free(free_event->trigger); in trace_events_free()
263 * trace_event_add_trigger - record an event trigger action
265 int trace_event_add_trigger(struct trace_events *event, char *trigger) in trace_event_add_trigger() argument
267 if (event->trigger) in trace_event_add_trigger()
268 free(event->trigger); in trace_event_add_trigger()
270 event->trigger = strdup(trigger); in trace_event_add_trigger()
271 if (!event->trigger) in trace_event_add_trigger()
307 * If the trigger is a hist: one, save the content of the hist file.
320 /* trigger enables hist */ in trace_event_save_hist()
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A 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 …]
|
| H A 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 …]
|
| /linux/Documentation/iio/ |
| H A 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 …]
|
| /linux/drivers/leds/ |
| H A D | led-triggers.c | 68 /* we come here only if buf matches no trigger */ in led_trigger_write()
99 led_cdev->trigger ? "none" : "[none]"); in led_trigger_format()
107 hit = led_cdev->trigger && !strcmp(led_cdev->trigger->name, trig->name); in led_trigger_format()
165 if (!led_cdev->trigger && !trig) in led_trigger_set()
169 event = kasprintf(GFP_KERNEL, "TRIGGER=%s", name); in led_trigger_set()
171 /* Remove any existing trigger */ in led_trigger_set()
172 if (led_cdev->trigger) { in led_trigger_set()
173 spin_lock(&led_cdev->trigger->leddev_list_lock); in led_trigger_set()
175 spin_unlock(&led_cdev->trigger->leddev_list_lock); in led_trigger_set()
182 device_remove_groups(led_cdev->dev, led_cdev->trigger->groups); in led_trigger_set()
[all …]
|
| /linux/drivers/scsi/mpt3sas/ |
| H A D | mpt3sas_trigger_diag.h | 46 /* Diagnostic Trigger Configuration Data Structures */
54 /* trigger types */
60 /* trigger names */
66 /* master trigger bitmask */
72 /* fake firmware event for trigger */
90 * struct SL_WH_EVENT_TRIGGER_T - Definition of an event trigger element
91 * @EventValue: Event Code to trigger on
106 * @EventTriggerEntry: List of Event trigger elements.
118 * struct SL_WH_SCSI_TRIGGER_T - Definition of a SCSI trigger element
136 * list of SCSI sense codes that should trigger a DIAG_SERVICE event when
[all …]
|
| /linux/Documentation/trace/coresight/ |
| H A 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 …]
|