Home
last modified time | relevance | path

Searched refs:fire (Results 1 – 25 of 26) sorted by relevance

12

/Linux-v5.4/sound/usb/6fire/
DMakefile2 snd-usb-6fire-objs += chip.o comm.o midi.o control.o firmware.o pcm.o
3 obj-$(CONFIG_SND_USB_6FIRE) += snd-usb-6fire.o
/Linux-v5.4/arch/m68k/include/asm/
Datari_joystick.h16 char fire; member
/Linux-v5.4/sound/usb/
DMakefile34 obj-$(CONFIG_SND) += misc/ usx2y/ caiaq/ 6fire/ hiface/ bcd2000/
DKconfig117 Say Y here to include support for TerraTec 6fire DMX USB interface.
/Linux-v5.4/Documentation/input/devices/
Drotary-encoder.rst76 able to fire on both edges.
Datarikbd.rst159 this mode the ikbd monitors the state of the Joystick 1 fire button at the
173 for the appropriate cursor motion keys. The trigger or fire buttons of the
509 %bbbbbbbb ; state of the JOYSTICK1 fire button packed
513 time-of-day clock, and monitor the fire button on Joystick 1. The fire button
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-bus-iio-timer-stm3292 and fire event when reach 0.
/Linux-v5.4/Documentation/timers/
Dtimers-howto.rst94 worst case, fire an interrupt for your upper bound.
Dtimekeeping.rst95 fire interrupts, so as to trigger events on the system timeline. On an SMP
/Linux-v5.4/Documentation/driver-api/rapidio/
Dmport_cdev.rst52 Supports blocking, asynchronous and posted (a.k.a 'fire-and-forget') data
/Linux-v5.4/Documentation/usb/
Dacm.rst130 If all this seems to be OK, fire up minicom and set it to talk to the ttyACM
/Linux-v5.4/Documentation/media/dvb-drivers/
Davermedia.rst105 In order to fire up the card, it is necessary to load a number
/Linux-v5.4/Documentation/RCU/
Drcubarrier.txt152 52 /* Wait for all RCU callbacks to fire. */
Dchecklist.txt241 latency. So please take advantage of kfree_rcu()'s "fire and
/Linux-v5.4/Documentation/networking/device_drivers/amazon/
Dena.txt114 fire.
/Linux-v5.4/
D.mailmap237 Simon Arlott <simon@octiron.net> <simon@fire.lp0.eu>
/Linux-v5.4/arch/xtensa/
DKconfig162 actually fire.
/Linux-v5.4/Documentation/filesystems/configfs/
Dconfigfs.txt478 are initialized. Every attribute store must fire off the connection if
/Linux-v5.4/Documentation/driver-api/thermal/
Dsysfs-api.rst786 queue to fire after a pre-determined number of seconds to start
/Linux-v5.4/Documentation/virt/kvm/
Dtimekeeping.txt584 Watchdog timers, such as the lock detector in Linux may fire accidentally when
/Linux-v5.4/Documentation/
Dkprobes.txt701 e. Watchpoint probes (which fire on data references).
/Linux-v5.4/Documentation/driver-api/gpio/
Ddriver.rst541 it does not make sense to fire interrupts on an output GPIO.
/Linux-v5.4/Documentation/scheduler/
Dsched-deadline.rst166 ActiveNonContending. The scheduler arms the "inactive timer" to fire at
/Linux-v5.4/Documentation/driver-api/
Dlibata.rst225 (``->bmdma_setup``), fire (``->bmdma_start``), and halt (``->bmdma_stop``) the
/Linux-v5.4/Documentation/virt/uml/
DUserModeLinux-HOWTO.txt2856 will fire up an xterm with gdb running in it.
3004 The standard drill in this sort of situation is to fire up gdb on the

12