| /OK3568_Linux_fs/kernel/arch/arm/boot/dts/ |
| H A D | rk3308-voice-module-mainboard-v10-aarch32.dtsi | 63 linux,default-trigger = "timer";
64 linux,default-trigger-delay-ms = <0>;
73 linux,default-trigger = "timer";
74 linux,default-trigger-delay-ms = <0>;
83 linux,default-trigger = "default-on";
90 linux,default-trigger = "timer";
91 linux,default-trigger-delay-ms = <100>;
100 linux,default-trigger = "timer";
101 linux,default-trigger-delay-ms = <100>;
110 linux,default-trigger = "default-on";
[all …]
|
| H A D | rk3036-echo.dts | 324 linux,default-trigger = "timer";
325 linux,default-trigger-delay-ms = <0>;
334 linux,default-trigger = "timer";
335 linux,default-trigger-delay-ms = <0>;
344 linux,default-trigger = "default-on";
351 linux,default-trigger = "timer";
352 linux,default-trigger-delay-ms = <100>;
361 linux,default-trigger = "timer";
362 linux,default-trigger-delay-ms = <100>;
371 linux,default-trigger = "default-on";
[all …]
|
| /OK3568_Linux_fs/kernel/arch/arm64/boot/dts/rockchip/ |
| H A D | rk3308bs-evb-amic-v11.dts | 61 linux,default-trigger = "timer";
62 linux,default-trigger-delay-ms = <0>;
71 linux,default-trigger = "timer";
72 linux,default-trigger-delay-ms = <0>;
81 linux,default-trigger = "default-on";
88 linux,default-trigger = "timer";
89 linux,default-trigger-delay-ms = <100>;
98 linux,default-trigger = "timer";
99 linux,default-trigger-delay-ms = <100>;
108 linux,default-trigger = "default-on";
[all …]
|
| H A D | rk3308-ai-va-v10.dts | 262 linux,default-trigger = "timer";
263 linux,default-trigger-delay-ms = <0>;
272 linux,default-trigger = "timer";
273 linux,default-trigger-delay-ms = <0>;
282 linux,default-trigger = "default-on";
289 linux,default-trigger = "timer";
290 linux,default-trigger-delay-ms = <100>;
299 linux,default-trigger = "timer";
300 linux,default-trigger-delay-ms = <100>;
309 linux,default-trigger = "default-on";
[all …]
|
| H A D | rk3308b-evb-v10.dtsi | 332 linux,default-trigger = "timer";
333 linux,default-trigger-delay-ms = <0>;
342 linux,default-trigger = "timer";
343 linux,default-trigger-delay-ms = <0>;
352 linux,default-trigger = "default-on";
359 linux,default-trigger = "timer";
360 linux,default-trigger-delay-ms = <100>;
369 linux,default-trigger = "timer";
370 linux,default-trigger-delay-ms = <100>;
379 linux,default-trigger = "default-on";
[all …]
|
| H A D | rk3308-evb-v11.dtsi | 388 linux,default-trigger = "timer";
389 linux,default-trigger-delay-ms = <0>;
398 linux,default-trigger = "timer";
399 linux,default-trigger-delay-ms = <0>;
408 linux,default-trigger = "default-on";
415 linux,default-trigger = "timer";
416 linux,default-trigger-delay-ms = <100>;
425 linux,default-trigger = "timer";
426 linux,default-trigger-delay-ms = <100>;
435 linux,default-trigger = "default-on";
[all …]
|
| H A D | rk3308-evb-v10.dtsi | 339 linux,default-trigger = "timer";
340 linux,default-trigger-delay-ms = <0>;
349 linux,default-trigger = "timer";
350 linux,default-trigger-delay-ms = <0>;
359 linux,default-trigger = "default-on";
366 linux,default-trigger = "timer";
367 linux,default-trigger-delay-ms = <100>;
376 linux,default-trigger = "timer";
377 linux,default-trigger-delay-ms = <100>;
386 linux,default-trigger = "default-on";
[all …]
|
| /OK3568_Linux_fs/kernel/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-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
|
| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/kernel/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 | 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, than the trigger turns the LED on and than 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
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/iio/adc/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/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 * @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 …]
|
| /OK3568_Linux_fs/kernel/kernel/trace/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/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"
75 tristate "LED activity Trigger"
[all …]
|
| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/external/xserver/present/ |
| H A D | present_fence.c | 38 SyncTrigger trigger; member
48 present_fence_sync_check_trigger(SyncTrigger *trigger, int64_t oldval) in present_fence_sync_check_trigger() argument
50 … struct present_fence *present_fence = container_of(trigger, struct present_fence, trigger); in present_fence_sync_check_trigger()
56 present_fence_sync_trigger_fired(SyncTrigger *trigger) in present_fence_sync_trigger_fired() argument
58 … struct present_fence *present_fence = container_of(trigger, struct present_fence, trigger); in present_fence_sync_trigger_fired()
65 present_fence_sync_counter_destroyed(SyncTrigger *trigger) in present_fence_sync_counter_destroyed() argument
67 … struct present_fence *present_fence = container_of(trigger, struct present_fence, trigger); in present_fence_sync_counter_destroyed()
82 present_fence->trigger.pSync = (SyncObject *) fence; in present_fence_create()
83 present_fence->trigger.CheckTrigger = present_fence_sync_check_trigger; in present_fence_create()
84 present_fence->trigger.TriggerFired = present_fence_sync_trigger_fired; in present_fence_create()
[all …]
|
| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/kernel/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 …]
|