| /Linux-v5.4/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 …]
|
| /Linux-v5.4/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
|
| D | overview.txt | 42 external signal (trigger). These triggers might be a data ready
45 capture or reading from a number of sensors. These triggers are
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | configfs-iio | 10 What: /config/iio/triggers
14 Industrial IO software triggers directory.
16 What: /config/iio/triggers/hrtimers
|
| D | sysfs-platform-dell-laptop | 27 This file allows to control the input triggers that
30 Read the file to see the triggers available. The ones
42 Note that not all the available triggers can be configured.
|
| D | sysfs-bus-iio-trigger-sysfs | 6 driver. Writing this file with any value triggers an event
38 created trigger from the list of available triggers. In order to
|
| D | sysfs-class-led | 50 You can change triggers in a similar manner to the way an IO
61 gpio and backlight triggers. In case of the backlight trigger,
|
| D | sysfs-driver-hid-corsair | 6 where G-keys triggers their regular key codes. "HW" for
|
| /Linux-v5.4/drivers/net/wireless/ath/ath9k/ |
| D | wow.c | 173 u8 triggers; in ath9k_suspend() local
213 triggers = ath9k_wow_map_triggers(sc, wowlan); in ath9k_suspend()
214 if (!triggers) { 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()
|
| /Linux-v5.4/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
|
| /Linux-v5.4/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,
|
| /Linux-v5.4/drivers/platform/x86/ |
| D | dell-laptop.c | 1124 u8 triggers; member
1134 u8 triggers; member
1197 info->triggers = buffer.output[2] & 0xFF; in kbd_get_info()
1284 state->triggers = (buffer.output[1] >> 16) & 0xFF; in kbd_get_state()
1304 input1 |= (state->triggers & 0xFF) << 16; in kbd_set_state()
1702 if (!(kbd_info.triggers & BIT(i))) in kbd_led_triggers_store()
1709 triggers_enabled && (state.triggers & BIT(i))) { in kbd_led_triggers_store()
1714 (!triggers_enabled || !(state.triggers & BIT(i)))) { in kbd_led_triggers_store()
1730 new_state.triggers |= BIT(trigger_bit); in kbd_led_triggers_store()
1732 new_state.triggers &= ~BIT(trigger_bit); in kbd_led_triggers_store()
[all …]
|
| /Linux-v5.4/kernel/trace/ |
| D | trace_events_trigger.c | 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()
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()
480 list_for_each_entry_safe(data, n, &file->triggers, list) { in clear_event_triggers()
504 list_for_each_entry_rcu(data, &file->triggers, list) { in update_cond_flag()
539 list_for_each_entry_rcu(test, &file->triggers, list) { in register_trigger()
552 list_add_rcu(&data->list, &file->triggers); in register_trigger()
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/dma/ |
| D | stm32-mdma.txt | 71 0x00: Each MDMA request triggers a buffer transfer (max 128 bytes)
72 0x01: Each MDMA request triggers a block transfer (max 64K bytes)
73 0x10: Each MDMA request triggers a repeated block transfer
74 0x11: Each MDMA request triggers a linked list transfer
|
| /Linux-v5.4/Documentation/devicetree/bindings/iio/adc/ |
| D | at91_adc.txt | 23 - atmel,adc-use-external-triggers: Boolean to enable the external triggers
56 atmel,adc-use-external-triggers;
|
| /Linux-v5.4/Documentation/hwmon/ |
| D | w83793.rst | 65 For voltage sensors, an alarm triggers if the measured value is below
67 For temperature sensors, an alarm triggers if the measured value goes
70 For fan sensors, an alarm triggers if the measured value is below the
101 If the case open alarm triggers, it will stay in this state unless cleared
|
| /Linux-v5.4/Documentation/driver-api/iio/ |
| D | triggers.rst | 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
|
| D | index.rst | 16 triggers
|
| /Linux-v5.4/Documentation/trace/ |
| D | events.rst | 309 6. Event triggers
316 with attached triggers is invoked, the set of trigger commands
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
371 triggers (you have to use '!' for each one added.)
[all …]
|
| /Linux-v5.4/Documentation/leds/ |
| D | leds-blinkm.rst | 18 a) LED class interface for use with triggers
38 assign triggers on each color.
|
| D | leds-class.rst | 15 nand-disk and sharpsl-charge triggers. With led triggers disabled, the code
18 Complex triggers while available to all LEDs have LED specific
27 You can change triggers in a similar manner to the way an IO scheduler
187 particular LED (ACPI?). The addition of triggers provided by the LED driver
|
| /Linux-v5.4/tools/perf/Documentation/ |
| D | Build.txt | 18 main makefile that triggers build of all perf objects including
36 The Makefile.perf triggers the build framework for build objects:
|
| /Linux-v5.4/drivers/iio/trigger/ |
| D | Kconfig | 3 # Industrial I/O standalone triggers
65 Provides support for using SYSFS entries as IIO triggers.
|
| /Linux-v5.4/drivers/iio/accel/ |
| D | bmc150-accel-core.c | 188 struct bmc150_accel_trigger triggers[BMC150_ACCEL_TRIGGERS]; member
755 if (data->triggers[i].indio_trig == trig) in bmc150_accel_validate_trigger()
1136 if (t == &t->data->triggers[BMC150_ACCEL_TRIGGER_DATA_READY]) in bmc150_accel_trig_try_reen()
1293 if (data->triggers[i].enabled) { in bmc150_accel_irq_handler()
1294 iio_trigger_poll(data->triggers[i].indio_trig); in bmc150_accel_irq_handler()
1331 if (data->triggers[i].indio_trig) { in bmc150_accel_unregister_triggers()
1332 iio_trigger_unregister(data->triggers[i].indio_trig); in bmc150_accel_unregister_triggers()
1333 data->triggers[i].indio_trig = NULL; in bmc150_accel_unregister_triggers()
1345 struct bmc150_accel_trigger *t = &data->triggers[i]; in bmc150_accel_triggers_setup()
|
| /Linux-v5.4/Documentation/devicetree/bindings/thermal/ |
| D | brcm,avs-tmon.txt | 8 - interrupts: temperature monitor interrupt, for high/low threshold triggers
|
