Home
last modified time | relevance | path

Searched refs:triggers (Results 1 – 25 of 27) sorted by relevance

12

/drivers/staging/iio/Documentation/
Dtrigger.txt3 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
Doverview.txt42 external signal (trigger). These triggers might be a data ready
45 capture or reading from a number of sensors. These triggers are
/drivers/net/wireless/ath/ath9k/
Dwow.c173 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()
/drivers/iio/
DKconfig30 (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
/drivers/platform/x86/
Ddell-laptop.c1136 u8 triggers; member
1146 u8 triggers; member
1214 info->triggers = buffer->output[2] & 0xFF; in kbd_get_info()
1308 state->triggers = (buffer->output[1] >> 16) & 0xFF; in kbd_get_state()
1330 buffer->input[1] |= (state->triggers & 0xFF) << 16; in kbd_set_state()
1732 if (!(kbd_info.triggers & BIT(i))) in kbd_led_triggers_store()
1739 triggers_enabled && (state.triggers & BIT(i))) { in kbd_led_triggers_store()
1744 (!triggers_enabled || !(state.triggers & BIT(i)))) { in kbd_led_triggers_store()
1760 new_state.triggers |= BIT(trigger_bit); in kbd_led_triggers_store()
1762 new_state.triggers &= ~BIT(trigger_bit); in kbd_led_triggers_store()
[all …]
DKconfig820 event handler to call when the PME triggers through _AEI and _L02
1042 will then remain awake until something triggers another suspend.
/drivers/staging/iio/trigger/
DKconfig2 # Industrial I/O standalone triggers
13 Provides support for using a Blackfin timer as IIO triggers.
/drivers/iio/accel/
Dbmc150-accel-core.c196 struct bmc150_accel_trigger triggers[BMC150_ACCEL_TRIGGERS]; member
763 if (data->triggers[i].indio_trig == trig) in bmc150_accel_validate_trigger()
1148 if (t == &t->data->triggers[BMC150_ACCEL_TRIGGER_DATA_READY]) in bmc150_accel_trig_try_reen()
1306 if (data->triggers[i].enabled) { in bmc150_accel_irq_handler()
1307 iio_trigger_poll(data->triggers[i].indio_trig); in bmc150_accel_irq_handler()
1344 if (data->triggers[i].indio_trig) { in bmc150_accel_unregister_triggers()
1345 iio_trigger_unregister(data->triggers[i].indio_trig); in bmc150_accel_unregister_triggers()
1346 data->triggers[i].indio_trig = NULL; in bmc150_accel_unregister_triggers()
1358 struct bmc150_accel_trigger *t = &data->triggers[i]; in bmc150_accel_triggers_setup()
/drivers/iio/trigger/
DKconfig2 # Industrial I/O standalone triggers
64 Provides support for using SYSFS entries as IIO triggers.
Dstm32-timer-trigger.c83 const void *triggers; member
371 const char * const *cur = priv->triggers; in stm32_setup_iio_triggers()
845 priv->triggers = triggers_table[index]; in stm32_timer_trigger_probe()
/drivers/iio/common/hid-sensors/
DKconfig12 HID sensor common processing for attributes and IIO triggers.
/drivers/infiniband/hw/hfi1/
Dsysfs.c619 "%u %u %u\n", temp.triggers & 0x1, in show_tempsense()
620 temp.triggers & 0x2, temp.triggers & 0x4); in show_tempsense()
Dhfi.h906 u8 triggers; /* temperature triggers */ member
/drivers/net/can/
DKconfig74 bool "Enable LED triggers for Netlink based drivers"
78 This option adds two LED triggers for packet receive and transmit
/drivers/leds/
DMakefile7 obj-$(CONFIG_LEDS_TRIGGERS) += led-triggers.o
DKconfig12 LEDs from both userspace and optionally, by kernel events (triggers).
/drivers/iio/adc/
Dat91_adc.c522 struct at91_adc_trigger *triggers, in at91_adc_get_trigger_value_by_name() argument
533 triggers[i].name); in at91_adc_get_trigger_value_by_name()
539 if (triggers[i].value == 0) in at91_adc_get_trigger_value_by_name()
541 return triggers[i].value; in at91_adc_get_trigger_value_by_name()
/drivers/staging/comedi/drivers/
Dcb_pcidas64.c2119 unsigned int triggers; in ai_cmdtest() local
2125 triggers = TRIG_TIMER; in ai_cmdtest()
2127 triggers |= TRIG_OTHER; in ai_cmdtest()
2129 triggers |= TRIG_FOLLOW; in ai_cmdtest()
2130 err |= comedi_check_trigger_src(&cmd->scan_begin_src, triggers); in ai_cmdtest()
2132 triggers = TRIG_TIMER; in ai_cmdtest()
2134 triggers |= TRIG_NOW; in ai_cmdtest()
2136 triggers |= TRIG_EXT; in ai_cmdtest()
2137 err |= comedi_check_trigger_src(&cmd->convert_src, triggers); in ai_cmdtest()
/drivers/net/wireless/marvell/libertas/
DREADME136 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
/drivers/leds/trigger/
DKconfig6 These triggers allow kernel events to drive the LEDs and can
/drivers/hwtracing/coresight/
DKconfig99 system triggers panic, the driver will parse context registers so
/drivers/net/phy/
DKconfig188 bool "Support LED triggers for tracking link state"
193 LED class driver. There are triggers for each link speed currently
/drivers/usb/
DKconfig180 This option adds LED triggers for USB host and/or gadget activity.
/drivers/macintosh/
DKconfig87 be triggered by any of the supported triggers. To get the
/drivers/watchdog/
DKconfig195 the watchdog triggers the system will be reset.
203 the watchdog triggers the system will be reset.
628 the watchdog triggers the system will be reset.

12