Searched full:complete (Results 1 – 25 of 383) sorted by relevance
12345678910>>...16
| /Documentation/scheduler/ |
| D | completion.rst | 17 calls and complete() instead.
40 - the signaling side through a call to complete() or complete_all().
65 complete(&early_console_added);
68 'complete' is not helpful unless the purpose is super obvious...
76 to prevent races with asynchronous complete() calls from occurring.
80 does not happen until all related activities (complete() or reinit_completion())
127 _killable() and _interruptible()) variants, the wait might complete
130 stack and cause subtle data corruption if a complete() is done in some
136 or has a lock or other synchronization mechanism to make sure complete()
160 wait_for_completion(&setup_done); complete(setup_done);
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-scsi_tape | 17 to and from the tape drive to complete. This includes all
24 to complete subtract read_ns and write_ns from this value.
65 read I/O requests to complete.
96 write I/O requests to complete.
|
| D | sysfs-class-fpga-manager | 34 * write complete = Doing post programming steps
35 * write complete error = Error while doing post programming
|
| D | sysfs-firmware-dmi-tables | 21 The complete DMI information can be obtained using these two
|
| /Documentation/userspace-api/media/dvb/ |
| D | frontend-stat-properties.rst | 64 measurement was not complete yet.
83 measurement was not complete yet.
114 measurement was not complete yet.
142 measurement was not complete yet.
171 measurement was not complete yet.
199 measurement was not complete yet.
220 measurement was not complete yet.
242 measurement was not complete yet.
|
| /Documentation/driver-api/dmaengine/ |
| D | client.rst | 307 stopped or until any running complete callbacks have finished. But it is
309 within a complete callback. dmaengine_synchronize() must be called before it
311 accessed from within the complete callback.
314 complete callbacks to finish before it returns. But the function must not be
315 called from atomic context or from within a complete callback.
336 4. Check Txn complete
344 the documentation in include/linux/dmaengine.h for a more complete
368 wait for the transfer and any running complete callbacks to finish before it
373 submitted descriptors or to free any resources accessed within the complete
|
| /Documentation/arm/ |
| D | cluster-pm-race-avoidance.rst | 119 CPU setup complete policy decision
127 policy decision CPU teardown complete
208 local CPU teardown complete
329 cluster-level setup and hardware coherency complete
336 Cluster-level setup is complete and hardware coherency is
354 Cluster-level setup is complete and hardware coherency is
430 coherency complete
469 initialisation: any other CPUs must wait for this to complete before
|
| /Documentation/admin-guide/device-mapper/ |
| D | statistics.rst | 82 that took 0-10 ms to complete, b is the number of requests
83 that took 10-20 ms to complete, c is the number of requests
84 that took 20-30 ms to complete and d is the number of
85 requests that took more than 30 ms to complete.
|
| /Documentation/admin-guide/media/ |
| D | bt8xx.rst | 21 Please see :doc:`bttv-cardlist` for a complete list of Cards based on the
107 For bug reports please send in a complete log with verbose=4 activated.
113 See :doc:`bttv-cardlist` for a complete list of
|
| /Documentation/driver-api/pm/ |
| D | notifiers.rst | 16 ``->resume()`` or even ``->prepare()`` and ``->complete()`` callbacks are not
21 from their ``->resume()`` or ``->complete()`` callback routines (user land
|
| D | devices.rst | 344 the ``->complete`` callback will be the next one invoked after the
348 Note that this direct-complete procedure applies even if the device is
360 these flags is set, the PM core will not apply the direct-complete
386 issuing the ``->complete`` callback).
428 ``resume_noirq``, ``resume_early``, ``resume``, ``complete``.
452 4. The ``complete`` phase should undo the actions of the ``prepare`` phase.
454 ``complete`` phase the device hierarchy is traversed bottom-up.
458 until the ``complete`` phase runs.
465 skipped). In that case, the ``->complete`` callback is entirely
469 the case, the ``->complete`` callback can consult the device's
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | dmic.txt | 12 - modeswitch-delay-ms: Delay (in ms) to complete DMIC mode switch
|
| /Documentation/RCU/ |
| D | rcubarrier.rst | 66 grace period to elapse, it does not wait for the callbacks to complete.
80 callbacks to complete. Please note that rcu_barrier() does **not** imply
179 for any pre-existing callbacks to complete.
195 RCU callbacks to complete.
267 4 complete(&rcu_barrier_completion);
334 state) before the grace period can complete. However, this is
|
| /Documentation/devicetree/bindings/clock/ |
| D | fixed-mmio-clock.txt | 5 It was designed for test systems, like FPGA, not for complete, finished SoCs.
|
| /Documentation/hwmon/ |
| D | sch5627.rst | 20 SMSC SCH5627 Super I/O chips include complete hardware monitoring
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-firmware-zynqmp | 75 The complete PS will be shut down, including the
79 The complete system/device is shut down.
|
| /Documentation/admin-guide/aoe/ |
| D | status.sh | 4 # A more complete version of this script is aoe-stat, in the
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-selinux-disable | 22 selinuxfs "disable" node and once that is complete we will start the
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux-gpmux.txt | 39 for the full duration of the complete multiplexed I2C transaction (i.e.
43 adapter for the complete multiplexed I2C transaction.
|
| /Documentation/crypto/ |
| D | async-tx-api.rst | 18 3.5 When does the operation complete?
97 operations complete. When an application needs to submit a chain of
121 3.5 When does the operation complete?
157 complete(cmp);
|
| /Documentation/driver-api/firmware/ |
| D | built-in-fw.rst | 27 a complete kernel rebuild.
|
| /Documentation/devicetree/bindings/input/rmi4/ |
| D | rmi_f01.txt | 5 bindings for devices which contain Function 1. Complete documentation
|
| /Documentation/devicetree/ |
| D | changesets.rst | 16 receiver sees a complete and consistent state of the tree when it
|
| /Documentation/driver-api/mmc/ |
| D | mmc-async-req.rst | 50 doesn't wait for the new request to complete. If there is no ongoing
78 /* start MMC transfer for the complete transfer size */
|
| /Documentation/core-api/ |
| D | padata.rst | 34 Then, complete padata initialization by allocating a padata_shell::
131 When a job does complete, parallel() (or whatever function actually finishes
153 It is the user's responsibility to ensure all outstanding jobs are complete
|
12345678910>>...16