Searched refs:fire (Results 1 – 25 of 32) sorted by relevance
12
| /linux/sound/usb/6fire/ |
| A D | .built-in.a.cmd | 1 …fire/built-in.a := echo >/dev/null; rm -f sound/usb/6fire/built-in.a; /usr/bin/ccache /home/test/w…
|
| A D | Makefile | 2 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/arch/m68k/include/asm/ |
| A D | atari_joystick.h | 16 char fire; member
|
| /linux/sound/usb/ |
| A D | .built-in.a.cmd | 1 …ilt-in.a sound/usb/usx2y/built-in.a sound/usb/caiaq/built-in.a sound/usb/6fire/built-in.a sound/us…
|
| A D | Makefile | 36 obj-$(CONFIG_SND) += misc/ usx2y/ caiaq/ 6fire/ hiface/ bcd2000/
|
| A D | Kconfig | 117 Say Y here to include support for TerraTec 6fire DMX USB interface.
|
| /linux/Documentation/ABI/testing/ |
| A D | sysfs-bus-iio-timer-stm32 | 110 and fire event when reach 0.
|
| /linux/Documentation/input/devices/ |
| A D | atarikbd.rst | 159 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
|
| A D | rotary-encoder.rst | 76 able to fire on both edges.
|
| /linux/Documentation/driver-api/rapidio/ |
| A D | mport_cdev.rst | 52 Supports blocking, asynchronous and posted (a.k.a 'fire-and-forget') data
|
| /linux/Documentation/timers/ |
| A D | timers-howto.rst | 94 worst case, fire an interrupt for your upper bound.
|
| A D | timekeeping.rst | 95 fire interrupts, so as to trigger events on the system timeline. On an SMP
|
| /linux/Documentation/usb/ |
| A D | acm.rst | 130 If all this seems to be OK, fire up minicom and set it to talk to the ttyACM
|
| /linux/Documentation/RCU/ |
| A D | rcubarrier.rst | 157 52 /* Wait for all RCU callbacks to fire. */
|
| A D | checklist.rst | 256 latency. So please take advantage of kfree_rcu()'s "fire and
|
| /linux/Documentation/dev-tools/ |
| A D | kcsan.rst | 243 address set up, and then observe the watchpoint to fire, two accesses to the
|
| /linux/Documentation/driver-api/ |
| A D | dma-buf.rst | 229 fences and controls when they fire. Mixing indefinite fences with normal
|
| /linux/arch/xtensa/ |
| A D | Kconfig | 171 actually fire.
|
| /linux/Documentation/networking/dsa/ |
| A D | sja1105.rst | 274 fact that no two gate actions (either tc-gate or tc-taprio gates) may fire at
|
| /linux/ |
| A D | .mailmap | 343 Simon Arlott <simon@octiron.net> <simon@fire.lp0.eu>
|
| /linux/Documentation/filesystems/ |
| A D | configfs.rst | 507 are initialized. Every attribute store must fire off the connection if
|
| A D | autofs.rst | 539 traps will not fire.
|
| /linux/Documentation/RCU/Design/Requirements/ |
| A D | Requirements.rst | 780 thread1() function's update, the WARN_ON() could never fire. But
783 the WARN_ON() can and does fire.
1315 kfree_rcu(), which allows “fire and forget” operation as shown
2563 means that timers posted to the outgoing CPU will not fire until late in
|
| /linux/Documentation/driver-api/gpio/ |
| A D | driver.rst | 561 it does not make sense to fire interrupts on an output GPIO.
|
| /linux/Documentation/virt/kvm/ |
| A D | timekeeping.rst | 615 Watchdog timers, such as the lock detector in Linux may fire accidentally when
|
Completed in 95 milliseconds
12