Searched full:wait (Results 1 – 25 of 360) sorted by relevance
12345678910>>...15
| /Documentation/locking/ |
| D | ww-mutex-design.rst | 2 Wound/Wait Deadlock-Proof Mutex Design
5 Please read mutex-design.rst first, as it applies to wait/wound mutexes too.
14 a handful of situations where the driver needs to wait for buffers to
37 and the deadlock handling approach is called Wait-Die. The name is based on
41 and dies. Hence Wait-Die.
42 There is also another algorithm called Wound-Wait:
46 transaction. Hence Wound-Wait.
48 However, the Wound-Wait algorithm is typically stated to generate fewer backoffs
49 compared to Wait-Die, but is, on the other hand, associated with more work than
50 Wait-Die when recovering from a backoff. Wound-Wait is also a preemptive
[all …]
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | gpio-restart.yaml | 25 inactive-delay, the GPIO is driven active again. After a delay specified by wait-delay, the
51 description: Delay (default 100) to wait after driving gpio active [ms]
56 description: Delay (default 100) to wait after driving gpio inactive [ms]
59 wait-delay:
61 description: Delay (default 3000) to wait after completing restart sequence [ms]
78 wait-delay = <3000>;
|
| D | gpio-poweroff.yaml | 40 description: Delay to wait after driving gpio active
44 description: Delay to wait after driving gpio inactive
51 description: Time to wait before assuming the power off sequence failed.
|
| /Documentation/devicetree/bindings/interconnect/ |
| D | qcom,bcm-voter.yaml | 24 qcom,tcs-wait:
26 Optional mask of which TCSs (Triggered Command Sets) wait for completion
27 upon triggering. If not specified, then the AMC and WAKE sets wait for
34 In most cases, it's necessary to wait in both the AMC and WAKE sets to
63 qcom,tcs-wait = <QCOM_ICC_TAG_AMC>;
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | ti,gpmc-child.yaml | 122 gpmc,wait-monitoring-ns:
123 description: Start of wait monitoring with regard to valid data
228 gpmc,wait-pin:
230 Wait-pin used by client. Must be less than "gpmc,num-waitpins".
233 ti,wait-pin-polarity:
235 Set the desired polarity for the selected wait pin.
240 gpmc,wait-on-read:
241 description: Enables wait monitoring on reads.
244 gpmc,wait-on-write:
245 description: Enables wait monitoring on writes.
|
| D | st,stm32-fmc2-ebi-props.yaml | 53 description: Wait signal polarity (NWAIT signal active high).
59 device are valid or if a wait state must be inserted when accessing
61 active one data cycle before wait state.
64 st,fmc2-ebi-cs-wait-enable:
66 account after the programmed latency period to insert wait states
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-arb-gpio-challenge.yaml | 45 4. Otherwise, wait for a few milliseconds and see if THEIR_CLAIMS are released.
46 5. If not, back off, release the claim and wait for a few more milliseconds.
66 Time to wait for a GPIO to go high.
75 wait-free-us:
80 wait-retry-us:
112 wait-retry-us = <3000>;
113 wait-free-us = <50000>;
|
| /Documentation/devicetree/bindings/mips/cavium/ |
| D | bootbus.txt | 46 - cavium,t-wait: A cell specifying the WAIT timing (in nS).
55 - cavium,wait-mode: Optional. If present, wait mode (WAITM) is selected.
95 cavium,t-wait = <0>;
115 cavium,t-wait = <0>;
120 cavium,wait-mode;
|
| /Documentation/devicetree/bindings/clock/ti/ |
| D | gate.txt | 17 "ti,wait-gate-clock" - gate clock which waits until clock is active before
28 "ti,composite-no-wait-gate-clock" - composite gate clock that does not wait
54 compatible = "ti,wait-gate-clock";
101 compatible = "ti,composite-no-wait-gate-clock";
|
| /Documentation/devicetree/bindings/misc/ |
| D | ifm-csi.txt | 14 - ifm,csi-wait-cycles: sensor bus wait cycles
34 ifm,csi-wait-cycles = <0>;
|
| /Documentation/scheduler/ |
| D | completion.rst | 2 Completions - "wait for completion" barrier APIs
8 If you have one or more threads that must wait for some kernel activity
46 it has to wait for it.
54 struct swait_queue_head wait;
57 This provides the ->wait waitqueue to place tasks on for waiting (if any), and
81 have taken place, even if these wait functions return prematurely due to a timeout
127 _killable() and _interruptible()) variants, the wait might complete
144 For a thread to wait for some concurrent activity to finish, it
173 The default behavior is to wait without a timeout and to mark the task as
211 The task is marked as TASK_UNINTERRUPTIBLE and will wait at most 'timeout'
[all …]
|
| /Documentation/userspace-api/media/mediactl/ |
| D | request-func-poll.rst | 13 request-poll - Wait for some event on a file descriptor
34 Timeout to wait for events
39 With the :c:func:`poll()` function applications can wait
|
| /Documentation/block/ |
| D | stat.rst | 32 read ticks milliseconds total wait time for read requests
36 write ticks milliseconds total wait time for write requests
39 time_in_queue milliseconds total wait time for all requests
43 discard ticks milliseconds total wait time for discard requests
45 flush ticks milliseconds total wait time for flush requests
81 example, if 60 read requests wait for an average of 30 ms, the read_ticks
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-func-poll.rst | 13 cec-poll - Wait for some event on a file descriptor
34 Timeout to wait for events
39 With the :c:func:`poll()` function applications can wait for CEC
|
| D | cec-ioc-receive.rst | 118 - The timeout in milliseconds. This is the time the device will wait
120 then it will wait indefinitely when it is called by :ref:`ioctl CEC_RECEIVE <CEC_RECEIVE>`.
131 In addition, if a non-blocking transmit will wait for a reply (ii.e. ``timeout``
146 - Wait until this message is replied. If ``reply`` is 0 and the
147 ``timeout`` is 0, then don't wait for a reply but return after
151 possible to send a message and wait up to ``timeout`` milliseconds for a
248 This flag makes it easier to wait for replies to vendor commands.
349 - The wait for a reply to an earlier transmitted message was aborted
372 The wait for a message was interrupted (e.g. by Ctrl-C).
400 The wait for a successful transmit was interrupted (e.g. by Ctrl-C).
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | fsl-imx-wdt.yaml | 57 fsl,suspend-in-wait:
60 If present, the watchdog device is suspended in WAIT mode
94 fsl,suspend-in-wait: false
|
| /Documentation/ABI/stable/ |
| D | sysfs-transport-srp | 12 Description: Number of seconds the SCSI layer will wait after a transport
21 Description: Number of seconds the SCSI layer will wait after a transport
37 Description: Number of seconds the SCSI layer will wait after a reconnect
|
| /Documentation/maintainer/ |
| D | maintainer-entry-profile.rst | 59 wait for the next -rc. At a minimum:
72 set will need to wait for the NEXT+1 merge window. Of course there is no
74 concluded by this point the expectation is the contributor should wait and
87 addition to specifying how long to wait before a resubmission this
|
| /Documentation/devicetree/bindings/bus/ |
| D | qcom,ebi2.yaml | 150 qcom,xmem-write-wait-cycles:
153 The number of wait cycles for every write access.
157 qcom,xmem-read-wait-cycles:
160 The number of wait cycles for every read access.
236 qcom,xmem-write-wait-cycles = <9>;
237 qcom,xmem-read-wait-cycles = <9>;
|
| /Documentation/driver-api/dmaengine/ |
| D | dmatest.rst | 92 To wait for test completion userspace can poll 'run' until it is false, or use
93 the wait parameter. Specifying 'wait=1' when loading the module causes module
95 /sys/module/dmatest/parameters/wait waits for any running test to complete
96 before returning. For example, the following scripts wait for 42 tests
102 % modprobe dmatest run=1 iterations=42 wait=1
108 % cat /sys/module/dmatest/parameters/wait
|
| /Documentation/devicetree/bindings/input/ |
| D | syna,rmi4.yaml | 46 Delay to wait after resetting the device.
50 Delay to wait after powering on the device.
82 The delay to wait after the last finger lift and the first doze
158 syna,rezero-wait-ms:
160 Time to wait after issuing a rezero command.
|
| /Documentation/devicetree/bindings/spi/ |
| D | arm,pl022-peripheral-props.yaml | 50 pl022,wait-state:
51 description: Microwire interface - Wait state
|
| /Documentation/devicetree/bindings/regulator/ |
| D | tps65090.txt | 24 - ti,overcurrent-wait: This is applicable to FET registers, which have a
25 poorly defined "overcurrent wait" field. If this property is present it
27 "overcurrent wait" field and we'll leave it to the BIOS/EC to deal with.
|
| /Documentation/driver-api/ |
| D | basics.rst | 60 Wait queues and Wake events
63 .. kernel-doc:: include/linux/wait.h
66 .. kernel-doc:: kernel/sched/wait.c
|
| /Documentation/RCU/ |
| D | rcu.rst | 12 from a linked list would first remove the item from the list, wait for
37 linked list, and then wait until all CPUs have switched context,
50 thing at a time, why should I wait for a grace period?
|
12345678910>>...15