Searched full:effects (Results 1 – 25 of 104) sorted by relevance
12345
| /Documentation/input/ |
| D | ff.rst | 17 effects.
73 - FF_CONSTANT can render constant force effects
74 - FF_PERIODIC can render periodic effects with the following waveforms:
83 - FF_RAMP can render ramp effects
86 - FF_DAMPER can simulate damper effects
87 - FF_RUMBLE rumble effects
105 Returns the number of effects the device can keep in its memory.
107 Uploading effects to the device
127 Effects are file descriptor specific.
149 This makes room for new effects in the device's memory. Note that this also
[all …]
|
| /Documentation/input/devices/ |
| D | iforce-protocol.rst | 16 specify force effects to I-Force 2.0 devices. None of this information comes
54 First, I describe effects that are sent by the device to the computer
74 Device effects states
96 00 Channel (when playing several effects at the same time, each must
236 Query number of effects
241 QUERY = 4e ('N'umber of effects)
243 The device should respond by sending the number of effects that can be played
245 ff 02 4e 14 CS would stand for 20 effects.
333 Bit 0 Stop all effects
350 Each device has a certain amount of memory to store parameters of effects.
[all …]
|
| /Documentation/networking/ |
| D | ipv6.rst | 27 The possible values and their effects are:
49 The possible values and their effects are:
67 The possible values and their effects are:
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-input.rst | 46 to this integer. Side effects are possible. For example inputs may
48 the current standard. Because of these possible side effects
|
| D | vidioc-g-output.rst | 47 pointer to this integer. Side effects are possible. For example outputs
50 effects applications must select an output before querying or
|
| D | dev-touch.rst | 37 environmental or edge effects.
|
| D | func-open.rst | 48 desired device name. This function has no side effects; all data format
|
| /Documentation/staging/ |
| D | speculation.rst | 5 This document explains potential effects of speculation, and how undesirable
6 effects can be mitigated portably using common APIs.
|
| /Documentation/devicetree/bindings/iio/temperature/ |
| D | mlx90632.txt | 16 Since measured object emissivity effects Infra Red energy emitted, emissivity
|
| D | adi,ltc2983.yaml | 148 parasitic resistance effects between the LTC2983 and the diode.
220 automatically remove parasitic thermocouple effects. Note that
300 automatically remove parasitic thermocouple effects.
|
| /Documentation/sound/cards/ |
| D | mixart.rst | 19 decoding, samplerate conversions and various effects.
75 - on-board effects and samplerate conversions
|
| D | audigy-mixer.rst | 37 low frequency effects (subwoofer signal)
316 FX8010 - A DSP Chip Architecture for Audio Effects
323 Audio Effects Processor with multiple asynchronous streams
327 Processor with Instruction Set for Audio Effects (Jan. 14, 1999)
330 Audio Effects Processor having Decoupled Instruction
341 Audio Effects Processor integrated on a single chip
347 Processor with Instruction Set for Audio Effects (Jul. 27, 1999)
|
| D | sb-live-mixer.rst | 51 low frequency effects (subwoofer signal)
321 FX8010 - A DSP Chip Architecture for Audio Effects
328 Audio Effects Processor with multiple asynchronous streams
332 Processor with Instruction Set for Audio Effects (Jan. 14, 1999)
335 Audio Effects Processor having Decoupled Instruction
346 Audio Effects Processor integrated on a single chip
352 Processor with Instruction Set for Audio Effects (Jul. 27, 1999)
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-func-open.rst | 38 desired device name. The function has no side effects; the device
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-func-open.rst | 47 desired device name. The function has no side effects; the device
|
| /Documentation/fb/ |
| D | metronomefb.rst | 32 a possibility that it could have some permanent effects on the display media.
|
| D | efifb.rst | 43 to workaround side-effects and slowdowns on other CPU cores
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | cpuacct.rst | 44 system times. This has two side effects:
|
| /Documentation/driver-api/pci/ |
| D | p2pdma.rst | 76 this way, the resource must be regular memory with no side effects.
133 effects behind it. Thus, the order of loads and stores should not be important
|
| /Documentation/userspace-api/media/ |
| D | gen-errors.rst | 91 Since errors may have side effects such as a driver reset,
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-driver-hid-roccat-kovaplus | 95 and light effects.
111 and light effects.
|
| D | sysfs-driver-hid-roccat-pyra | 84 and light effects.
100 and light effects.
|
| /Documentation/ |
| D | memory-barriers.txt | 74 (*) Inter-CPU acquiring barrier effects.
85 (*) Kernel I/O barrier effects.
89 (*) The effects of the cpu cache.
143 So in the above diagram, the effects of the memory operations performed by a
416 time the barrier completes, the effects of all the stores prior to that
533 indirect effect will be the order in which the second CPU sees the effects
536 (*) There is no guarantee that a CPU will see the correct order of effects
543 mechanisms should propagate the indirect effects of a memory barrier
704 Either can result in highly counterintuitive effects on ordering.
1104 Makes sure all effects ---> \ ddddddddddddddddd | |
[all …]
|
| /Documentation/scsi/ |
| D | lpfc.rst | 37 to reappear or link come back alive, with no inadvertent side effects
|
| /Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 56 problems when enabling multiple bus segments (a command with side effects
|
12345