| /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-5.10/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-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 | 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
45 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-driver-hid-corsair | 6 where G-keys triggers their regular key codes. "HW" for
|
| D | sysfs-class-led | 70 You can change triggers in a similar manner to the way an IO
81 gpio and backlight triggers. In case of the backlight trigger,
|
| /kernel/linux/linux-5.10/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()
|
| /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/drivers/platform/x86/ |
| D | dell-laptop.c | 1147 u8 triggers; member
1157 u8 triggers; member
1220 info->triggers = buffer.output[2] & 0xFF; in kbd_get_info()
1307 state->triggers = (buffer.output[1] >> 16) & 0xFF; in kbd_get_state()
1327 input1 |= (state->triggers & 0xFF) << 16; in kbd_set_state()
1728 if (!(kbd_info.triggers & BIT(i))) in kbd_led_triggers_store()
1735 triggers_enabled && (state.triggers & BIT(i))) { in kbd_led_triggers_store()
1740 (!triggers_enabled || !(state.triggers & BIT(i)))) { in kbd_led_triggers_store()
1756 new_state.triggers |= BIT(trigger_bit); in kbd_led_triggers_store()
1758 new_state.triggers &= ~BIT(trigger_bit); in kbd_led_triggers_store()
[all …]
|
| /kernel/linux/linux-5.10/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()
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()
487 list_for_each_entry_safe(data, n, &file->triggers, list) { in clear_event_triggers()
513 list_for_each_entry(data, &file->triggers, list) { in update_cond_flag()
550 list_for_each_entry(test, &file->triggers, list) { in register_trigger()
563 list_add_rcu(&data->list, &file->triggers); in register_trigger()
[all …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/ftrace/test.d/ |
| D | functions | 18 # remove action triggers first
33 reset_trigger() { # reset all current setting triggers
47 reset_ftrace_filter() { # reset all triggers in set_ftrace_filter
88 # no events, no triggers, no filters, no function filters,
|
| /kernel/linux/linux-5.10/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;
|
| /kernel/linux/linux-5.10/Documentation/driver-api/iio/ |
| D | triggers.rst | 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
|
| D | index.rst | 16 triggers
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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:
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | ptp.rst | 81 - 2 Time stamp external triggers, programmable polarity (opt. interrupt)
90 - GPIO inputs can time stamp external triggers
104 - Programmable inputs can time stamp external triggers
|
| /kernel/linux/linux-5.10/drivers/iio/trigger/ |
| D | Kconfig | 3 # Industrial I/O standalone triggers
65 Provides support for using SYSFS entries as IIO triggers.
|
| /kernel/linux/linux-5.10/drivers/iio/accel/ |
| D | bmc150-accel-core.c | 188 struct bmc150_accel_trigger triggers[BMC150_ACCEL_TRIGGERS]; member
763 if (data->triggers[i].indio_trig == trig) in bmc150_accel_validate_trigger()
1145 if (t == &t->data->triggers[BMC150_ACCEL_TRIGGER_DATA_READY]) in bmc150_accel_trig_try_reen()
1302 if (data->triggers[i].enabled) { in bmc150_accel_irq_handler()
1303 iio_trigger_poll(data->triggers[i].indio_trig); in bmc150_accel_irq_handler()
1340 if (data->triggers[i].indio_trig) { in bmc150_accel_unregister_triggers()
1341 iio_trigger_unregister(data->triggers[i].indio_trig); in bmc150_accel_unregister_triggers()
1342 data->triggers[i].indio_trig = NULL; in bmc150_accel_unregister_triggers()
1354 struct bmc150_accel_trigger *t = &data->triggers[i]; in bmc150_accel_triggers_setup()
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/thermal/ |
| D | brcm,avs-tmon.txt | 11 - interrupts: temperature monitor interrupt, for high/low threshold triggers,
|
| /kernel/linux/linux-5.10/fs/jbd2/ |
| D | transaction.c | 1422 struct jbd2_buffer_trigger_type *triggers) in jbd2_buffer_frozen_trigger() argument
1426 if (!triggers || !triggers->t_frozen) in jbd2_buffer_frozen_trigger()
1429 triggers->t_frozen(triggers, bh, mapped_data, bh->b_size); in jbd2_buffer_frozen_trigger()
1433 struct jbd2_buffer_trigger_type *triggers) in jbd2_buffer_abort_trigger() argument
1435 if (!triggers || !triggers->t_abort) in jbd2_buffer_abort_trigger()
1438 triggers->t_abort(triggers, jh2bh(jh)); in jbd2_buffer_abort_trigger()
|