Searched full:operation (Results 1 – 25 of 755) sorted by relevance
12345678910>>...31
| /Documentation/gpu/ |
| D | drm-vm-bind-async.rst | 15 * ``VM_BIND``: An operation or a list of operations to modify a gpu_vm using
24 * ``in-syncobj``: Argument to a VM_BIND IOCTL, the VM_BIND operation waits
27 * ``out-syncobj``: Argument to a VM_BIND_IOCTL, the VM_BIND operation
28 signals these when the bind operation is complete.
57 operation. VM_BIND operations that use the same bind context can be
66 Synchronous / Asynchronous VM_BIND operation
86 immediately available for preparing the asynchronous operation.
89 the in-syncobjs needs to signal before the first operation starts to
90 execute, and the out-syncobjs signal after the last operation
91 completes. Operations in the operation list can be assumed, where it
[all …]
|
| /Documentation/crypto/ |
| D | async-tx-api.rst | 17 3.4 When does the operation execute?
18 3.5 When does the operation complete?
35 that is written to the API can optimize for asynchronous operation and
51 operation will be offloaded when an engine is available and carried out
55 API automatically handles cases where the transition from one operation
57 3. dmaengine extensions to support multiple clients and operation types
69 async_<operation>(<op specific parameters>, struct async_submit_ctl *submit)
94 The return value is non-NULL and points to a 'descriptor' when the operation
109 3.4 When does the operation execute?
113 async_<operation> call. Offload engine drivers batch operations to
[all …]
|
| D | userspace-if.rst | 61 user space application. User space invokes the cipher operation with the
62 send()/write() system call family. The result of the cipher operation is
83 In-place Cipher operation
86 Just like the in-kernel operation of the kernel crypto API, the user
87 space interface allows the cipher operation in-place. That means that
96 operation.
101 The message digest type to be used for the cipher operation is selected
135 key is not set the HMAC operation is performed without the initial HMAC state
141 The operation is very similar to the message digest discussion. During
168 - specification of the cipher operation type with one of these flags:
[all …]
|
| D | architecture.rst | 57 Synchronous And Asynchronous Operation
63 When using the synchronous API operation, the caller invokes a cipher
64 operation which is performed synchronously by the kernel crypto API.
65 That means, the caller waits until the cipher operation completes.
67 For synchronous operation, the set of API calls is small and
70 Asynchronous operation is provided by the kernel crypto API which
71 implies that the invocation of a cipher operation will complete almost
72 instantly. That invocation triggers the cipher operation but it does not
73 signal its completion. Before invoking a cipher operation, the caller
75 signal the completion of the cipher operation. Furthermore, the caller
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | fe-set-frontend.rst | 31 Points to parameters for tuning operation.
36 This ioctl call starts a tuning operation using specified parameters.
38 and the tuning could be initiated. The result of the tuning operation in
42 operation is initiated before the previous one was completed, the
43 previous operation will be aborted in favor of the new one. This command
|
| /Documentation/driver-api/pldmfw/ |
| D | driver-ops.rst | 13 The ``.match_record`` operation is used to determine whether a given PLDM
19 The ``.match_record`` operation should return true if a given record matches
25 The ``.send_package_data`` operation is used to send the device-specific
34 The ``.send_component_table`` operation is used to forward component
47 The ``.flash_component`` operation is used to inform the device driver to
54 The ``.finalize_update`` operation is used by the ``pldmfw`` library in
|
| /Documentation/filesystems/iomap/ |
| D | design.rst | 64 largest space mappings that it can create for a given file operation and
67 operation being performed, which enables it to combat fragmentation with
73 At a high level, an iomap operation `looks like this
76 1. For each byte in the operation range...
87 3. Increment operation cursor
91 Each iomap operation will be covered in more detail below.
136 * **iomap internal operation lock**: This is a general term for
142 * **pure overwrite**: A write operation that does not require any
184 operation because writes must allocate and map space, and return
206 For a write or writeback operation, the ioend should update the
[all …]
|
| /Documentation/litmus-tests/ |
| D | README | 25 Demonstrate that a failing cmpxchg() operation acts as a full barrier
29 Demonstrate that a failing cmpxchg() operation acts as an acquire
30 operation when followed by smp_mb__after_atomic().
33 Demonstrate that a failing cmpxchg() operation does not act as a
37 Demonstrate that a failing cmpxchg() operation does not act as an
38 acquire operation.
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | tvp7002.txt | 21 0 = Normal Operation (Active Low, Default)
22 1 = Inverted operation
25 Under normal operation, the field ID output is set to logic 1 for an odd field
27 0 = Normal Operation (Active Low, Default)
|
| D | dongwoon,dw9768.yaml | 43 - 1 # AAC2 mode(operation time# 0.48 x Tvib)
44 - 2 # AAC3 mode(operation time# 0.70 x Tvib)
45 - 3 # AAC4 mode(operation time# 0.75 x Tvib)
46 - 5 # AAC8 mode(operation time# 1.13 x Tvib)
|
| /Documentation/litmus-tests/atomic/ |
| D | cmpxchg-fail-unordered-2.litmus | 6 * Demonstrate that a failing cmpxchg() operation does not act as either
7 * an acquire release operation. (In contrast, a successful cmpxchg()
8 * does act as both an acquire and a release operation.)
|
| /Documentation/sound/designs/ |
| D | channel-mapping-api.rst | 52 Each control element provides at least the TLV read operation and the
53 read operation. Optionally, the write operation can be provided to
59 The TLV operation gives the list of available channel
144 Read Operation
147 The control read operation is for providing the current channel map of
155 Write Operation
158 The control write operation is optional, and only for devices that can
163 This operation is allowed only at PCM PREPARED state. When called in
|
| D | compress-accel.rst | 27 - separate buffers (input + output) for each operation
98 operation is executed before. If seqno is zero, operation is executed for all
115 If the multiple tasks require a state handling (e.g. resampling operation),
118 for the new operation rather using open/close mechanism.
122 Stop (dequeues) a task. If seqno is zero, operation is executed for all
|
| /Documentation/filesystems/ |
| D | directory-locking.rst | 56 * if the parents don't have a common ancestor, fail the operation.
61 target is not a descendent of source; fail the operation otherwise.
72 There is one more thing to consider - splicing. It's not an operation
117 For some filesystems a method can involve a directory operation on
118 another filesystem; it may be ecryptfs doing operation in the underlying
122 directory operation on this filesystem might involve directory operations
124 it should be possible to rank the filesystems so that directory operation
185 Each operation in the minimal cycle must have locked at least
221 of another - otherwise the operation would not have progressed past
254 the only operation that could introduce loops is cross-directory rename.
[all …]
|
| /Documentation/core-api/ |
| D | union_find.rst | 21 returning a “representative element” of that set. This operation
37 the find operation, and using union by rank can reduce the time complexity
38 of the union operation. These optimizations reduce the average time
39 complexity of each find and union operation to O(α(n)), where α(n) is the
64 operation, the tree with the smaller rank is attached under the tree with the
84 This operation is mainly used to determine whether two nodes belong to the same
86 During the find operation, path compression is performed to improve the
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 18 result for an operation ... it doesn't indicate that anything is wrong
51 Also returned when trying to invoke an I2C operation in an
53 to execute some other operation.
72 detected before any I/O operation was started. Use a more
77 performing an I/O operation. Use a more specific fault
102 Returned by an adapter when asked to perform an operation
128 This is returned by drivers when an operation took too much
131 SMBus adapters may return it when an operation took more
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-ppi | 30 This attribute shows the request for an operation to be
40 This attribute shows the response to the most recent operation
51 a requested operation. The format is "<action num>: <action
60 operation to be executed in the pre-OS environment by the BIOS
71 operation to be executed in the pre-OS environment by the BIOS
|
| D | sysfs-bus-iio-dac | 9 - disable toggle operation;
11 - enable toggle operation.
40 - disable toggle operation;
42 - enable toggle operation.
|
| /Documentation/arch/arm/ |
| D | firmware.rst | 24 To call a firmware operation, a helper macro is provided::
29 the macro checks if the operation is provided and calls it or otherwise returns
30 -ENOSYS to signal that given operation is not available (for example, to allow
31 fallback to legacy operation).
61 Example of using a firmware operation::
|
| /Documentation/arch/xtensa/ |
| D | atomctl.rst | 2 Atomic Operation Control (ATOMCTL) Register
5 We Have Atomic Operation Control (ATOMCTL) Register.
27 support the Internal Operation.
49 2 Internal Operation Internal Operation Reserved
|
| /Documentation/devicetree/bindings/mtd/ |
| D | nand-macronix.txt | 4 Macronix NANDs support randomizer operation for scrambling user data,
7 for program operation, i.e., tPROG 300us to 340us (randomizer enabled).
9 operation.
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | blkio-controller.rst | 152 are further divided by the type of operation - read or write, sync
154 device, third field specifies the operation type and the fourth field
159 are further divided by the type of operation - read or write, sync
161 device, third field specifies the operation type and the fourth field
173 the type of operation - read or write, sync or async. First two fields
175 specifies the operation type and the fourth field specifies the
188 devices too. This time is further divided by the type of operation -
190 minor number of the device, third field specifies the operation type
195 cgroup. This is further divided by the type of operation - read or
200 cgroup. This is further divided by the type of operation - read or
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | tps6105x.txt | 25 Example (GPIO operation only):
34 Example (GPIO + regulator operation):
49 Example (GPIO + led operation):
|
| /Documentation/networking/ |
| D | nfc.rst | 63 * stop_poll - stop on progress polling operation
66 * data_exchange - send data and receive the response (transceive operation)
72 exchange operation.
81 * NFC_CMD_STOP_POLL - stop the polling operation in a specific device
92 operation by calling STOP_POLL command. In this case, it will be checked if
95 If the polling operation finds one or more targets, the event TARGETS_FOUND is
|
| /Documentation/userspace-api/netlink/ |
| D | genetlink-legacy.rst | 130 Requests and responses for operation ``a`` will have the ID of 1,
132 ``value`` it's previous operation ``+ 1``). Notification ``c`` will
133 use the ID of 4, operation ``d`` 5 etc.
144 ``reply`` sections of the operations (if an operation has both ``do``
175 If operation ``d`` does not set ``values`` explicitly in the spec
176 it will be allocated 3 for the request (``a`` is the previous operation
178 the previous operation in the "from-kernel" direction).
238 or overridden for each operation.
286 New Netlink families should never respond to a DO operation with multiple
|
12345678910>>...31