Searched refs:fire (Results 1 – 25 of 30) sorted by relevance
12
| /Linux-v5.10/sound/usb/6fire/ |
| 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-v5.10/arch/m68k/include/asm/ |
| D | atari_joystick.h | 16 char fire; member
|
| /Linux-v5.10/sound/usb/ |
| D | Makefile | 35 obj-$(CONFIG_SND) += misc/ usx2y/ caiaq/ 6fire/ hiface/ bcd2000/
|
| D | Kconfig | 117 Say Y here to include support for TerraTec 6fire DMX USB interface.
|
| /Linux-v5.10/Documentation/input/devices/ |
| D | rotary-encoder.rst | 76 able to fire on both edges.
|
| 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
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-timer-stm32 | 110 and fire event when reach 0.
|
| /Linux-v5.10/Documentation/driver-api/rapidio/ |
| D | mport_cdev.rst | 52 Supports blocking, asynchronous and posted (a.k.a 'fire-and-forget') data
|
| /Linux-v5.10/Documentation/timers/ |
| D | timers-howto.rst | 94 worst case, fire an interrupt for your upper bound.
|
| D | timekeeping.rst | 95 fire interrupts, so as to trigger events on the system timeline. On an SMP
|
| /Linux-v5.10/Documentation/usb/ |
| D | acm.rst | 130 If all this seems to be OK, fire up minicom and set it to talk to the ttyACM
|
| /Linux-v5.10/Documentation/driver-api/ |
| D | dma-buf.rst | 204 fences and controls when they fire. Mixing indefinite fences with normal
|
| /Linux-v5.10/Documentation/networking/device_drivers/ethernet/amazon/ |
| D | ena.rst | 121 fire.
|
| /Linux-v5.10/Documentation/RCU/ |
| D | rcubarrier.rst | 157 52 /* Wait for all RCU callbacks to fire. */
|
| D | checklist.rst | 245 latency. So please take advantage of kfree_rcu()'s "fire and
|
| /Linux-v5.10/Documentation/dev-tools/ |
| D | kcsan.rst | 243 address set up, and then observe the watchpoint to fire, two accesses to the
|
| /Linux-v5.10/ |
| D | .mailmap | 303 Simon Arlott <simon@octiron.net> <simon@fire.lp0.eu>
|
| /Linux-v5.10/arch/xtensa/ |
| D | Kconfig | 167 actually fire.
|
| /Linux-v5.10/Documentation/driver-api/thermal/ |
| D | sysfs-api.rst | 772 queue to fire after a pre-determined number of seconds to start
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | configfs.rst | 507 are initialized. Every attribute store must fire off the connection if
|
| D | autofs.rst | 539 traps will not fire.
|
| /Linux-v5.10/Documentation/networking/dsa/ |
| D | sja1105.rst | 488 fact that no two gate actions (either tc-gate or tc-taprio gates) may fire at
|
| /Linux-v5.10/Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 779 ``thread1()`` function's update, the ``WARN_ON()`` could never fire. But
782 the ``WARN_ON()`` can and does fire.
1314 ``kfree_rcu()``, which allows “fire and forget” operation as shown
2533 means that timers posted to the outgoing CPU will not fire until late in
|
| /Linux-v5.10/Documentation/trace/ |
| D | kprobes.rst | 702 e. Watchpoint probes (which fire on data references).
|
| /Linux-v5.10/Documentation/virt/kvm/ |
| D | timekeeping.rst | 615 Watchdog timers, such as the lock detector in Linux may fire accidentally when
|
12
