Home
last modified time | relevance | path

Searched full:done (Results 1 – 25 of 838) sorted by relevance

12345678910>>...34

/Documentation/translations/zh_CN/scheduler/
Dcompletion.rst33 事件被简化为 ``struct completion`` 中的一个简单标志,被恰如其名地称为‘done’。
49 完成标记为 "done",这是完全正常的。
55 unsigned int done;
84 init_completion(&dynamic_object->done);
86 在这个调用中,我们初始化 waitqueue 并将 ->done 设置为 0,即“not completed”或
87 “not done”。
89 重新初始化函数reinit_completion(),只是将->done字段重置为0(“not done”),而
104 注意,在这种情况下,完成在启动时(或模块加载时)被初始化为“not done”,不需要调用
134 void wait_for_completion(struct completion *done)
180 int wait_for_completion_interruptible(struct completion *done)
[all …]
/Documentation/scheduler/
Dcompletion.rst27 is reduced to a simple flag in 'struct completion', appropriately called "done".
45 to have marked a completion as 'done' before another thread checks whether
53 unsigned int done;
58 the ->done completion flag for indicating whether it's completed or not.
84 Initializing of dynamically allocated completion objects is done via a call to
87 init_completion(&dynamic_object->done);
89 In this call we initialize the waitqueue and set ->done to 0, i.e. "not completed"
90 or "not done".
93 ->done field to 0 ("not done"), without touching the waitqueue.
111 initialized to 'not done' and doesn't require an init_completion() call.
[all …]
/Documentation/devicetree/bindings/fpga/
Dlattice,sysconfig.yaml17 Programming of ECP5 is done by writing uncompressed bitstream image in .bit
40 done-gpios:
42 A GPIO line connected to DONE (active high) pin of the device.
79 done-gpios = <&gpio3 2 GPIO_ACTIVE_HIGH>;
Dxlnx,fpga-selectmap.yaml42 done-gpios:
44 config status pin (referred to as DONE in the manual)
69 - done-gpios
82 done-gpios = <&gpio2 30 GPIO_ACTIVE_HIGH>;
Dxlnx,fpga-slave-serial.yaml44 done-gpios:
46 config status pin (referred to as DONE in the manual)
59 - done-gpios
77 done-gpios = <&gpio0 9 GPIO_ACTIVE_HIGH>;
/Documentation/ABI/stable/
Dsysfs-class-bluetooth7 The reset may or may not be done through the device transport
8 (e.g., UART/USB), and can also be done through an out-of-band
Dsysfs-bus-mhi7 one attempt to power up the device has been done. If read
18 at least one attempt to power up the device has been done. If
/Documentation/livepatch/
Dsystem-state.rst17 done by the already installed livepatches.
32 or by the newly used code. Also it must be possible to find changes done by
69 The check is done when the livepatch is enabled. The rules are:
94 been done by a livepatch that is being replaced.
100 done by livepatches that were being replaced.
125 - Clean up its own mess in case of error. It might be done by a custom
/Documentation/netlink/specs/
Dhandshake.yaml75 name: done
113 name: done
115 attribute-set: done
/Documentation/core-api/
Dpadata.rst9 Padata is a mechanism by which the kernel can farm jobs out to be done in
77 Changing the CPU masks are expensive operations, so it should not be done with
93 structure specific to the work to be done. Most of its fields are private to
96 be called in the process of getting the work done as we will see
99 The submission of the job is done with::
106 done; it must be in the current instance's CPU mask (if not the cb_cpu pointer
119 information about the actual work to be done is probably obtained by using
/Documentation/ABI/testing/
Dsysfs-class-fc21 If an appid_store is done for a cgroup id that already
26 from a cgroup, an appid_store should be done with the
Dsysfs-memory-page-offline13 The offlining is done in kernel specific granularity.
38 The offlining is done in kernel specific granularity.
/Documentation/mm/
Dbalance.rst35 would not be done even when the dma zone was completely empty. 2.2 has
40 In 2.3, zone balancing can be done in one of two ways: depending on the
73 primarily needed in a situation where balancing can not be done,
80 Page stealing from process memory and shm is done if stealing the page would
91 That decision is not hysteresis based, and is done when the number of free
/Documentation/ABI/obsolete/
Dsysfs-driver-hid-roccat-kovaplus8 Has never been used. If bookkeeping is done, it's done in userland tools.
29 Has never been used. If bookkeeping is done, it's done in userland tools.
39 Has never been used. If bookkeeping is done, it's done in userland tools.
/Documentation/admin-guide/device-mapper/
Dunstriped.rst59 done
64 done;
69 done;
73 done
80 done
Dkcopyd.rst10 to set aside for their copy jobs. This is done with a call to
43 When a user is done with all their copy jobs, they should call
/Documentation/sound/soc/
Djack.rst18 This is done by splitting the jacks up into three things working
52 Actual jack detection is done by code which is able to monitor some
58 Often this is done based on the status of a GPIO - a handler for this is
/Documentation/sphinx/
Dautomarkup.py5 # has been done.
81 done = 0
112 if m.start() > done:
113 repl.append(nodes.Text(t[done:m.start()]))
121 done = m.end()
122 if done < len(t):
123 repl.append(nodes.Text(t[done:]))
/Documentation/maintainer/
Drebasing-and-merging.rst27 referred to as rebasing since both are done with the ``git rebase``
80 likely, invalidates much of the testing that was done. A reparented
123 merge, say *why* the merge is being done. For a lower-level tree, "why" is
191 merge has been done. Take a moment to do it right; people will read those
196 bringing in other bugs and should almost never be done. If that subsystem
210 the development cycle in order to pick up changes and fixes done elsewhere
222 arisen and be prepared to explain why something abnormal needs to be done.
/Documentation/misc-devices/
Dxilinx_sdfec.rst136 Setting the order is done by using the ioctl :c:macro:`XSDFEC_SET_ORDER`
138 Setting the order can only be done if the following restrictions are met:
155 Adding LDPC codes can only be done if the following restrictions are met:
164 Configuring the Turbo decode parameters is done by using the ioctl :c:macro:`XSDFEC_SET_TURBO` usin…
166 Adding Turbo decode can only be done if the following restrictions are met:
174 Enabling or disabling interrupts is done by using the ioctl :c:macro:`XSDFEC_SET_IRQ`. The members …
184 Bypassing the SD-FEC is done by using the ioctl :c:macro:`XSDFEC_SET_BYPASS`
186 Bypassing the SD-FEC can only be done if the following restrictions are met:
/Documentation/devicetree/bindings/mmc/
Dsynopsys-dw-mshc-common.yaml53 Data done irq is expected if data length is less than
56 data done irq. Add this watermark quirk to mark this requirement and
/Documentation/admin-guide/mm/
Dsoft-dirty.rst10 This is done by writing "4" into the ``/proc/PID/clear_refs`` file of the
17 This is done by reading from the ``/proc/PID/pagemap``. The bit 55 of the
/Documentation/features/scripts/
Dfeatures-refresh.sh52 done
95 done
98 done
/Documentation/trace/
Dtracepoints.rst93 Connecting a function (probe) to a tracepoint is done by providing a
95 register_trace_subsys_eventname(). Removing a probe is done through
106 occur. Name mangling of the tracepoints is done using the prototypes
108 is done at the registration site by the compiler. Tracepoints can be
/Documentation/driver-api/
Dregulator.rst94 operating voltage for their cards. This may be done while the regulator
118 Registration should be triggered by explicit setup done by the platform,
133 :c:type:`regulator_consumer_supply`. This is done at driver registration
146 This is done at driver registration time` by providing a

12345678910>>...34