| /linux-4.1.27/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.
22 triggers to keep track of what they have created.
33 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-4.1.27/drivers/staging/iio/trigger/ |
| D | Kconfig | 2 # Industrial I/O standalone triggers
9 tristate "Periodic RTC triggers"
13 clocks as IIO triggers.
23 Provides support for using a Blackfin timer as IIO triggers.
|
| /linux-4.1.27/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-4.1.27/drivers/platform/x86/ |
| D | dell-laptop.c | 991 u8 triggers; member
1001 u8 triggers; member
1063 info->triggers = buffer->output[2] & 0xFF; in kbd_get_info()
1153 state->triggers = (buffer->output[1] >> 16) & 0xFF; in kbd_get_state()
1172 buffer->input[1] |= (state->triggers & 0xFF) << 16; in kbd_set_state()
1536 if (!(kbd_info.triggers & BIT(i))) in kbd_led_triggers_store()
1543 triggers_enabled && (state.triggers & BIT(i))) in kbd_led_triggers_store()
1546 (!triggers_enabled || !(state.triggers & BIT(i)))) in kbd_led_triggers_store()
1556 new_state.triggers |= BIT(trigger_bit); in kbd_led_triggers_store()
1558 new_state.triggers &= ~BIT(trigger_bit); in kbd_led_triggers_store()
[all …]
|
| D | Kconfig | 875 will then remain awake until something triggers another suspend.
|
| /linux-4.1.27/kernel/trace/ |
| D | trace_events_trigger.c | 72 if (list_empty(&file->triggers)) in event_triggers_call()
75 list_for_each_entry_rcu(data, &file->triggers, list) { in event_triggers_call()
111 list_for_each_entry_rcu(data, &file->triggers, list) { in event_triggers_post_call()
127 return seq_list_next(t, &event_file->triggers, pos); in trigger_next()
140 if (list_empty(&event_file->triggers)) in trigger_start()
143 return seq_list_start(&event_file->triggers, *pos); in trigger_start()
473 list_for_each_entry_rcu(data, &file->triggers, list) { in clear_event_triggers()
496 list_for_each_entry_rcu(data, &file->triggers, list) { in update_cond_flag()
530 list_for_each_entry_rcu(test, &file->triggers, list) { in register_trigger()
543 list_add_rcu(&data->list, &file->triggers); in register_trigger()
[all …]
|
| D | trace_events.c | 1859 INIT_LIST_HEAD(&file->triggers); in trace_create_new_event()
|
| /linux-4.1.27/drivers/iio/trigger/ |
| D | Kconfig | 2 # Industrial I/O standalone triggers
22 Provides support for using SYSFS entries as IIO triggers.
|
| /linux-4.1.27/Documentation/leds/ |
| D | leds-class.txt | 18 nand-disk and sharpsl-charge triggers. With led triggers disabled, the code
21 Complex triggers whilst available to all LEDs have LED specific
30 You can change triggers in a similar manner to the way an IO scheduler
95 particular LED (ACPI?). The addition of triggers provided by the LED driver
|
| D | leds-blinkm.txt | 14 a) LED class interface for use with triggers
33 assign triggers on each color.
|
| D | ledtrig-transient.txt | 27 triggers.
30 triggers it supports and a default trigger. During registration, activation
42 being able to actually change the LED state. Once driver is resumed, triggers
|
| /linux-4.1.27/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-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-class-led | 25 You can change triggers in a similar manner to the way an IO
35 gpio and backlight triggers. In case of the backlight trigger,
|
| 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
|
| D | sysfs-bus-iio-frequency-ad9523 | 25 Writing '1' triggers the clock distribution synchronization
|
| D | sysfs-firmware-gsmi | 7 triggers. Some of the callbacks are similar to those
|
| D | sysfs-class-led-flash | 43 Flash strobe state. When written with 1 it triggers flash strobe
|
| D | sysfs-firmware-acpi | 195 * and it triggers an ACPI fixed event when the enable bit is set again
|
| D | sysfs-class-mic.txt | 57 When written, this sysfs entry triggers different state change
|
| D | sysfs-bus-coresight-devices-etm3x | 126 Description: (RW) Defines which event triggers a trace.
|
| D | sysfs-bus-iio | 45 effects data ready triggers, hardware buffers and the sysfs
|
| /linux-4.1.27/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-4.1.27/Documentation/hwmon/ |
| D | w83793 | 58 For voltage sensors, an alarm triggers if the measured value is below
60 For temperature sensors, an alarm triggers if the measured value goes
63 For fan sensors, an alarm triggers if the measured value is below the
94 If the case open alarm triggers, it will stay in this state unless cleared
|
| D | pc87360 | 113 associated low, high and overtemperature limits, each of which triggers an
151 triggers an alarm when crossed.
163 If an alarm triggers, it will remain triggered until the hardware register
168 a once-only alarm triggers, it may take 2 seconds for it to show, and 2
|
| D | tmp401 | 54 file triggers a reset.
|
| D | adc128d818 | 35 If an alarm triggers, it will remain triggered until the hardware register
|
| D | smsc47m1 | 53 If an alarm triggers, it will remain triggered until the hardware register
|
| D | f71805f | 93 triggers an alarm when crossed.
115 has a high limit, those crossing triggers an alarm. There is an associated
|
| D | lm80 | 55 If an alarm triggers, it will remain triggered until the hardware register
|
| D | vt1211 | 99 Each measured voltage has an associated low and high limit which triggers an
107 has a high limit which triggers an alarm if crossed. There is an associated
|
| D | lm78 | 60 If an alarm triggers, it will remain triggered until the hardware register
|
| D | lm87 | 50 If an alarm triggers, it will remain triggered until the hardware register
|
| D | gl518sm | 65 If an alarm triggers, it will remain triggered until the hardware register
|
| D | via686a | 58 If an alarm triggers, it will remain triggered until the hardware register
|
| D | sis5595 | 92 If an alarm triggers, it will remain triggered until the hardware register
|
| D | adm1026 | 67 If an alarm triggers, it will remain triggered until the hardware register
|
| D | adm1021 | 81 If an alarm triggers, it will remain triggered until the hardware register
|
| D | smm665 | 82 or crit if exceeding the limits triggers RST, Power Off, or Fault, and as min or
|
| D | w83792d | 92 which triggers if your computer case is open (This one is latched, contrary
|
| D | w83781d | 119 chips which triggers if your computer case is open.
144 If an alarm triggers, it will remain triggered until the hardware register
|
| D | it87 | 193 If an alarm triggers, it will remain triggered until the hardware register
|
| D | dme1737 | 138 fan tachometers. All 6 inputs have an associated min limit which triggers an
|
| /linux-4.1.27/Documentation/trace/ |
| D | events.txt | 291 6. Event triggers
298 with attached triggers is invoked, the set of trigger commands
308 A given event can have any number of triggers associated with it,
312 Event triggers are implemented on top of "soft" mode, which means that
313 whenever a trace event has one or more triggers associated with it,
317 This scheme allows triggers to be invoked even for events that aren't
319 used for conditionally invoking triggers.
321 The syntax for event triggers is roughly based on the syntax for
349 triggers (you have to use '!' for each one added.)
392 Note that there can be any number of enable/disable_event triggers
[all …]
|
| D | events-kmem.txt | 81 which triggers a mm_page_pcpu_drain event.
|
| D | ftrace.txt | 2454 as long as there's a command that triggers it.
|
| /linux-4.1.27/drivers/iio/ |
| D | Kconfig | 48 Provides IIO core support for triggers. Currently these
50 buffers. The triggers are effectively a 'capture
|
| /linux-4.1.27/fs/jbd2/ |
| D | transaction.c | 1214 struct jbd2_buffer_trigger_type *triggers) in jbd2_buffer_frozen_trigger() argument
1218 if (!triggers || !triggers->t_frozen) in jbd2_buffer_frozen_trigger()
1221 triggers->t_frozen(triggers, bh, mapped_data, bh->b_size); in jbd2_buffer_frozen_trigger()
1225 struct jbd2_buffer_trigger_type *triggers) in jbd2_buffer_abort_trigger() argument
1227 if (!triggers || !triggers->t_abort) in jbd2_buffer_abort_trigger()
1230 triggers->t_abort(triggers, jh2bh(jh)); in jbd2_buffer_abort_trigger()
|
| /linux-4.1.27/drivers/iio/accel/ |
| D | bmc150-accel.c | 190 struct bmc150_accel_trigger triggers[BMC150_ACCEL_TRIGGERS]; member
836 if (data->triggers[i].indio_trig == trig) in bmc150_accel_validate_trigger()
1239 if (t == &t->data->triggers[BMC150_ACCEL_TRIGGER_DATA_READY]) in bmc150_accel_trig_try_reen()
1391 if (data->triggers[i].enabled) { in bmc150_accel_irq_handler()
1392 iio_trigger_poll(data->triggers[i].indio_trig); in bmc150_accel_irq_handler()
1469 if (data->triggers[i].indio_trig) { in bmc150_accel_unregister_triggers()
1470 iio_trigger_unregister(data->triggers[i].indio_trig); in bmc150_accel_unregister_triggers()
1471 data->triggers[i].indio_trig = NULL; in bmc150_accel_unregister_triggers()
1482 struct bmc150_accel_trigger *t = &data->triggers[i]; in bmc150_accel_triggers_setup()
|
| /linux-4.1.27/drivers/iio/common/hid-sensors/ |
| D | Kconfig | 12 HID sensor common processing for attributes and IIO triggers.
|
| /linux-4.1.27/fs/ocfs2/ |
| D | journal.c | 505 static inline struct ocfs2_triggers *to_ocfs2_trigger(struct jbd2_buffer_trigger_type *triggers) in to_ocfs2_trigger() argument
507 return container_of(triggers, struct ocfs2_triggers, ot_triggers); in to_ocfs2_trigger()
510 static void ocfs2_frozen_trigger(struct jbd2_buffer_trigger_type *triggers, in ocfs2_frozen_trigger() argument
514 struct ocfs2_triggers *ot = to_ocfs2_trigger(triggers); in ocfs2_frozen_trigger()
529 static void ocfs2_dq_frozen_trigger(struct jbd2_buffer_trigger_type *triggers, in ocfs2_dq_frozen_trigger() argument
549 static void ocfs2_db_frozen_trigger(struct jbd2_buffer_trigger_type *triggers, in ocfs2_db_frozen_trigger() argument
565 static void ocfs2_abort_trigger(struct jbd2_buffer_trigger_type *triggers, in ocfs2_abort_trigger() argument
653 struct ocfs2_triggers *triggers, in __ocfs2_journal_access() argument
699 if (!status && ocfs2_meta_ecc(osb) && triggers) in __ocfs2_journal_access()
700 jbd2_journal_set_triggers(bh, &triggers->ot_triggers); in __ocfs2_journal_access()
|
| /linux-4.1.27/Documentation/ptp/ |
| D | ptp.txt | 75 - 2 Time stamp external triggers, programmable polarity (opt. interrupt)
83 - GPIO inputs can time stamp external triggers
|
| /linux-4.1.27/Documentation/x86/x86_64/ |
| D | machinecheck | 40 finds MCEs it triggers an exponential speedup (poll more often) on
42 triggers an exponential backoff (poll less often) on the polling
|
| /linux-4.1.27/Documentation/powerpc/ |
| D | ptrace.txt | 101 - set a watchpoint which triggers on reads in the second watchpoint register
111 - set a watchpoint which triggers only with a specific value
|
| D | eeh-pci-error-recovery.txt | 176 which causes uevents to go out to user space. This triggers
182 which restarts the device driver and triggers more user-space
|
| D | hvcs.txt | 336 driver manages. Writing a '1' to the attribute triggers the update. An
|
| /linux-4.1.27/Documentation/isdn/ |
| D | README.pcbit | 28 - The driver often triggers errors in the board that I and the
|
| /linux-4.1.27/drivers/gpio/ |
| D | gpio-pca953x.c | 452 u8 trigger[MAX_BANK], triggers = 0; in pca953x_irq_pending() local
475 triggers += trigger[i]; in pca953x_irq_pending()
478 if (!triggers) in pca953x_irq_pending()
|
| /linux-4.1.27/drivers/leds/ |
| D | Makefile | 6 obj-$(CONFIG_LEDS_TRIGGERS) += led-triggers.o
|
| D | Kconfig | 12 LEDs from both userspace and optionally, by kernel events (triggers).
|
| /linux-4.1.27/drivers/net/can/ |
| D | Kconfig | 56 bool "Enable LED triggers for Netlink based drivers"
60 This option adds two LED triggers for packet receive and transmit
|
| /linux-4.1.27/Documentation/devicetree/bindings/leds/ |
| D | common.txt | 23 string defining the trigger assigned to the LED. Current triggers are:
|
| /linux-4.1.27/Documentation/input/ |
| D | edt-ft5x06.txt | 49 files triggers a new readout. It is recommended to provide a buffer
|
| D | gamepad.txt | 142 reported as "right" triggers (BTN_TR/ABS_HAT1X).
|
| D | iforce-protocol.txt | 77 Val x+1 = Button x triggers the effect
|
| D | xpad.txt | 45 and the zero-setting is not correct for the triggers (I don't know if that
|
| /linux-4.1.27/drivers/iio/adc/ |
| D | at91_adc.c | 515 struct at91_adc_trigger *triggers, in at91_adc_get_trigger_value_by_name() argument
526 triggers[i].name); in at91_adc_get_trigger_value_by_name()
532 if (triggers[i].value == 0) in at91_adc_get_trigger_value_by_name()
534 return triggers[i].value; in at91_adc_get_trigger_value_by_name()
|
| /linux-4.1.27/drivers/net/wireless/libertas/ |
| D | README | 136 triggers the LINK_LOSS event. This event is generated only once after
143 triggers the generation of the MAX_FAIL event. Once this event is
|
| /linux-4.1.27/include/linux/ |
| D | jbd2.h | 1077 struct jbd2_buffer_trigger_type *triggers);
1079 struct jbd2_buffer_trigger_type *triggers);
|
| D | ftrace_event.h | 370 struct list_head triggers; member
|
| /linux-4.1.27/drivers/staging/comedi/drivers/ |
| D | cb_pcidas64.c | 2084 unsigned int triggers; in ai_cmdtest() local
2090 triggers = TRIG_TIMER; in ai_cmdtest()
2092 triggers |= TRIG_OTHER; in ai_cmdtest()
2094 triggers |= TRIG_FOLLOW; in ai_cmdtest()
2095 err |= comedi_check_trigger_src(&cmd->scan_begin_src, triggers); in ai_cmdtest()
2097 triggers = TRIG_TIMER; in ai_cmdtest()
2099 triggers |= TRIG_NOW; in ai_cmdtest()
2101 triggers |= TRIG_EXT; in ai_cmdtest()
2102 err |= comedi_check_trigger_src(&cmd->convert_src, triggers); in ai_cmdtest()
|
| /linux-4.1.27/drivers/leds/trigger/ |
| D | Kconfig | 6 These triggers allow kernel events to drive the LEDs and can
|
| /linux-4.1.27/Documentation/devicetree/bindings/soc/ti/ |
| D | keystone-navigator-dma.txt | 5 channels and flows for the QMSS(Queue Manager SubSystem) who triggers
|
| D | keystone-navigator-qmss.txt | 64 accumulator triggers an interrupt to the host to read
|
| /linux-4.1.27/net/mac80211/ |
| D | Kconfig | 85 bool "Enable LED triggers"
90 This option enables a few LED triggers for different
|
| /linux-4.1.27/arch/powerpc/boot/dts/ |
| D | acadia.dts | 176 * that it uses to generate snapshot triggers. We
|
| /linux-4.1.27/Documentation/x86/ |
| D | entry_64.txt | 95 triggers three main behavior changes:
|
| /linux-4.1.27/drivers/usb/ |
| D | Kconfig | 158 This option adds LED triggers for USB host and/or gadget activity.
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,idle-state.txt | 17 interrupt to trigger the core back in to active. This triggers the cache
|
| /linux-4.1.27/Documentation/laptops/ |
| D | asus-laptop.txt | 75 kernel triggers like ide-disk or heartbeat.
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | uvcvideo.txt | 41 triggers a read or write of the associated XU control.
|
| /linux-4.1.27/ |
| D | REPORTING-BUGS | 117 [7.] A small shell script or example program which triggers the
|
| /linux-4.1.27/Documentation/blockdev/ |
| D | floppy.txt | 121 interrupt latency, but it triggers more interrupts (i.e. it
|
| /linux-4.1.27/Documentation/power/ |
| D | charger-manager.txt | 184 Charger Manager, a charger device driver that triggers the event can call
|
| /linux-4.1.27/drivers/macintosh/ |
| D | Kconfig | 97 be triggered by any of the supported triggers. To get the
|
| /linux-4.1.27/Documentation/s390/ |
| D | driver-model.txt | 242 Piping 'on' to an online chpid triggers path reprobing for all devices
|
| D | s390dbf.txt | 86 There are currently 2 possible triggers, which stop the debug feature
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | f2fs.txt | 227 the number is less than this value, it triggers
563 cleaner is operated by a kernel thread, and triggers the cleaning job when the
|
| D | fuse.txt | 393 | [close fd] | [FLUSH triggers 'magic' flag]
|
| D | spufs.txt | 213 triggers an interrupt on the SPU. The value written to the signal
|
| D | xfs-delayed-logging-design.txt | 663 path that triggers a CIL flush (i.e. whatever triggers the log force) will enter
|
| /linux-4.1.27/Documentation/ia64/ |
| D | fsys.txt | 205 breakpoint that triggers at any privilege level other than 3 (user-mode).
|
| /linux-4.1.27/Documentation/ |
| D | sysrq.txt | 152 Note that this just triggers a crash if there is no dump mechanism available.
|
| D | xillybus.txt | 298 but it doesn't block. There is also an autoflushing mechanism, which triggers
|
| D | atomic_ops.txt | 398 BUG() triggers since obj->active
|
| D | md.txt | 518 triggers a poll event. Sometimes the value will briefly be
|
| D | kernel-parameters.txt | 1356 On systems that have PCI, it triggers scanning the
|
| /linux-4.1.27/arch/arm/boot/dts/ |
| D | at91sam9rl.dtsi | 260 atmel,adc-use-external-triggers;
|
| D | at91sam9260.dtsi | 931 atmel,adc-use-external-triggers;
|
| D | at91sam9x5.dtsi | 994 atmel,adc-use-external-triggers;
|
| D | sama5d3.dtsi | 322 atmel,adc-use-external-triggers;
|
| /linux-4.1.27/Documentation/device-mapper/ |
| D | thin-provisioning.txt | 115 Resuming a device with a new table itself triggers an event so the
|
| /linux-4.1.27/drivers/watchdog/ |
| D | Kconfig | 123 the watchdog triggers the system will be reset.
131 the watchdog triggers the system will be reset.
471 the watchdog triggers the system will be reset.
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | unified-hierarchy.txt | 265 - The event isn't recursive. It triggers when a cgroup doesn't have
|
| /linux-4.1.27/Documentation/networking/ |
| D | scaling.txt | 68 Each receive queue has a separate IRQ associated with it. The NIC triggers
|
| /linux-4.1.27/Documentation/usb/ |
| D | power-management.txt | 646 3/ Port resume always triggers an attached child device to resume. After a
|
| /linux-4.1.27/net/netfilter/ |
| D | Kconfig | 733 added. When the timer expires, it triggers a sysfs notification.
|
| /linux-4.1.27/drivers/scsi/aic7xxx/ |
| D | aic7xxx.seq | 1229 * last as it triggers the computation of
|