Searched refs:fire (Results 1 – 25 of 30) sorted by relevance
12
2 snd-usb-6fire-objs += chip.o comm.o midi.o control.o firmware.o pcm.o3 obj-$(CONFIG_SND_USB_6FIRE) += snd-usb-6fire.o
16 char fire; member
35 obj-$(CONFIG_SND) += misc/ usx2y/ caiaq/ 6fire/ hiface/ bcd2000/
117 Say Y here to include support for TerraTec 6fire DMX USB interface.
76 able to fire on both edges.
159 this mode the ikbd monitors the state of the Joystick 1 fire button at the173 for the appropriate cursor motion keys. The trigger or fire buttons of the509 %bbbbbbbb ; state of the JOYSTICK1 fire button packed513 time-of-day clock, and monitor the fire button on Joystick 1. The fire button
110 and fire event when reach 0.
94 worst case, fire an interrupt for your upper bound.
95 fire interrupts, so as to trigger events on the system timeline. On an SMP
52 Supports blocking, asynchronous and posted (a.k.a 'fire-and-forget') data
130 If all this seems to be OK, fire up minicom and set it to talk to the ttyACM
204 fences and controls when they fire. Mixing indefinite fences with normal
121 fire.
157 52 /* Wait for all RCU callbacks to fire. */
245 latency. So please take advantage of kfree_rcu()'s "fire and
243 address set up, and then observe the watchpoint to fire, two accesses to the
303 Simon Arlott <simon@octiron.net> <simon@fire.lp0.eu>
167 actually fire.
772 queue to fire after a pre-determined number of seconds to start
507 are initialized. Every attribute store must fire off the connection if
539 traps will not fire.
488 fact that no two gate actions (either tc-gate or tc-taprio gates) may fire at
779 ``thread1()`` function's update, the ``WARN_ON()`` could never fire. But782 the ``WARN_ON()`` can and does fire.1314 ``kfree_rcu()``, which allows “fire and forget” operation as shown2533 means that timers posted to the outgoing CPU will not fire until late in
702 e. Watchpoint probes (which fire on data references).
543 it does not make sense to fire interrupts on an output GPIO.
