| /Linux-v5.4/drivers/greybus/ |
| D | operation.c | 22 /* Workqueue to handle Greybus operation completions. */
29 * Protects updates to operation->errno.
33 static int gb_operation_response_send(struct gb_operation *operation,
37 * Increment operation active count and add to connection list unless the
40 * Caller holds operation reference.
42 static int gb_operation_get_active(struct gb_operation *operation) in gb_operation_get_active() argument
44 struct gb_connection *connection = operation->connection; in gb_operation_get_active()
52 if (gb_operation_is_incoming(operation)) in gb_operation_get_active()
56 if (!gb_operation_is_core(operation)) in gb_operation_get_active()
63 if (operation->active++ == 0) in gb_operation_get_active()
[all …]
|
| D | greybus_trace.h | 71 * Occurs after an operation has been canceled, possibly before the
92 TP_PROTO(struct gb_operation *operation),
94 TP_ARGS(operation),
98 __field(u16, id) /* Operation ID */
107 __entry->cport_id = operation->connection->hd_cport_id;
108 __entry->id = operation->id;
109 __entry->type = operation->type;
110 __entry->flags = operation->flags;
111 __entry->active = operation->active;
112 __entry->waiters = atomic_read(&operation->waiters);
[all …]
|
| /Linux-v5.4/include/linux/ |
| D | ccp.h | 45 * ccp_enqueue_cmd - queue an operation for processing by the CCP
61 * the result of the operation.
105 * ccp_aes_mode - AES operation mode
129 * ccp_aes_mode - AES operation mode
131 * @CCP_AES_ACTION_DECRYPT: AES decrypt operation
132 * @CCP_AES_ACTION_ENCRYPT: AES encrypt operation
144 * struct ccp_aes_engine - CCP AES operation
145 * @type: AES operation key size
146 * @mode: AES operation mode
147 * @action: AES operation (decrypt/encrypt)
[all …]
|
| D | nvme-fc-driver.h | 98 * to LLDD in order to perform a NVME FCP IO operation.
115 * the FCP operation. req argument is the pointer to the original
116 * FCP IO operation.
117 * @private: pointer to memory allocated alongside the FCP operation
119 * while processing the operation. The length of the buffer
123 * Values set by the LLDD indicating completion status of the FCP operation.
128 * @status: Completion status of the FCP operation. must be 0 upon success,
131 * status of the FCP operation at the NVME-FC level.
269 * access it during runtime operation.
535 * the specific FC-NVME IU operation(s) to perform
[all …]
|
| /Linux-v5.4/include/linux/greybus/ |
| D | operation.h | 25 * The top bit of the type in an operation message header indicates
53 struct gb_operation *operation; member
73 * A Greybus operation is a remote procedure call performed over a
76 * Every operation consists of a request message sent to the other
78 * the sender. Every operation has a type, whose interpretation is
81 * Only four things in an operation structure are intended to be
82 * directly usable by protocol handlers: the operation's connection
83 * pointer; the operation type; the request message payload (and
87 * In addition, every operation has a result, which is an errno
88 * value. Protocol handlers access the operation result using
[all …]
|
| /Linux-v5.4/Documentation/filesystems/caching/ |
| D | operations.txt | 11 (*) Operation record initialisation.
37 OPERATION RECORD INITIALISATION
40 An operation is recorded in an fscache_operation struct:
52 Someone wanting to issue an operation should allocate something with this
58 with the operation to be initialised and the release function to use.
67 operation and waited for afterwards.
74 There are a number of parameters that can be set in the operation record's flag
78 (1) The operation may be done synchronously (FSCACHE_OP_MYTHREAD). A thread
79 may decide it wants to handle an operation itself without deferring it to
89 before submitting the operation, and the operating thread must wait for it
[all …]
|
| /Linux-v5.4/include/trace/events/ |
| D | block.h | 67 * @q: queue holding operation
68 * @rq: block IO operation request
70 * The block operation request @rq is being placed back into queue
105 * block_rq_complete - block IO operation completed by device driver
111 * of operation request has been completed by the device driver. If
183 * block_rq_insert - insert block operation request into queue
185 * @rq: block IO operation request
187 * Called immediately before block operation request @rq is inserted
188 * into queue @q. The fields in the operation request @rq struct can
190 * operation would access.
[all …]
|
| /Linux-v5.4/sound/soc/qcom/qdsp6/ |
| D | q6dsp-errno.h | 7 /* Success. The operation completed with no errors. */
11 /* Bad operation parameter. */
13 /* Unsupported routine or operation. */
25 /* Operation is already processed. */
27 /* Operation is not ready to be processed. */
29 /* Operation is pending completion. */
31 /* Operation could not be accepted or processed. */
33 /* Operation aborted due to an error. */
35 /* Operation preempted by a higher priority. */
37 /* Operation requests intervention to complete. */
[all …]
|
| /Linux-v5.4/arch/arm/mm/ |
| D | cache-uniphier.c | 31 /* operation registers */
32 #define UNIPHIER_SSCOPE 0x244 /* Cache Operation Primitive Entry */
38 #define UNIPHIER_SSCOQM 0x248 /* Cache Operation Queue Mode */
46 #define UNIPHIER_SSCOQAD 0x24c /* Cache Operation Queue Address */
47 #define UNIPHIER_SSCOQSZ 0x250 /* Cache Operation Queue Size */
48 #define UNIPHIER_SSCOPPQSEF 0x25c /* Cache Operation Queue Set Complete*/
51 #define UNIPHIER_SSCOLPQS 0x260 /* Cache Operation Queue Status */
56 /* Is the operation region specified by address range? */
65 * @op_base: virtual base address of operation registers
69 * @range_op_max_size: max size that can be handled by a single range operation
[all …]
|
| /Linux-v5.4/tools/perf/pmu-events/arch/arm64/ |
| D | armv8-recommended.json | 213 "PublicDescription": "Exclusive operation speculatively executed, LDREX or LDX",
216 "BriefDescription": "Exclusive operation speculatively executed, LDREX or LDX"
219 "PublicDescription": "Exclusive operation speculatively executed, STREX or STX pass",
222 "BriefDescription": "Exclusive operation speculatively executed, STREX or STX pass"
225 "PublicDescription": "Exclusive operation speculatively executed, STREX or STX fail",
228 "BriefDescription": "Exclusive operation speculatively executed, STREX or STX fail"
231 "PublicDescription": "Exclusive operation speculatively executed, STREX or STX",
234 "BriefDescription": "Exclusive operation speculatively executed, STREX or STX"
237 "PublicDescription": "Operation speculatively executed, load",
240 "BriefDescription": "Operation speculatively executed, load"
[all …]
|
| /Linux-v5.4/tools/perf/pmu-events/arch/arm64/hisilicon/hip08/ |
| D | core-imp-def.json | 105 …"PublicDescription": "No any micro operation is issued and meanwhile any load operation is not res…
108 …"BriefDescription": "No any micro operation is issued and meanwhile any load operation is not reso…
111 …"PublicDescription": "No any micro operation is issued and meanwhile there is any load operation m…
114 …"BriefDescription": "No any micro operation is issued and meanwhile there is any load operation mi…
117 …"PublicDescription": "No any micro operation is issued and meanwhile there is any load operation m…
120 …"BriefDescription": "No any micro operation is issued and meanwhile there is any load operation mi…
|
| /Linux-v5.4/Documentation/crypto/ |
| D | async-tx-api.txt | 11 3.4 When does the operation execute?
12 3.5 When does the operation complete?
30 that is written to the API can optimize for asynchronous operation and
44 operation will be offloaded when an engine is available and carried out
48 API automatically handles cases where the transition from one operation
50 3/ dmaengine extensions to support multiple clients and operation types
57 async_<operation>(<op specific parameters>, struct async_submit ctl *submit)
76 The return value is non-NULL and points to a 'descriptor' when the operation
90 3.4 When does the operation execute?
92 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 operation is performed without the initial HMAC state change caused by
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 …]
|
| /Linux-v5.4/include/asm-generic/ |
| D | bitops-instrumented.h | 21 * This is a relaxed atomic operation (no implied memory barriers).
38 * region of memory concurrently, the effect may be that only one operation
52 * This is a relaxed atomic operation (no implied memory barriers).
66 * region of memory concurrently, the effect may be that only one operation
80 * This operation is atomic and provides release barrier semantics.
93 * This is a non-atomic operation but implies a release barrier before the
94 * memory operation. It can be used for an unlock if no other CPUs can
108 * This is a relaxed atomic operation (no implied memory barriers).
125 * region of memory concurrently, the effect may be that only one operation
139 * This is an atomic fully-ordered operation (implied full memory barrier).
[all …]
|
| /Linux-v5.4/security/tomoyo/ |
| D | file.c | 169 [r->param.path.operation], in tomoyo_audit_path_log()
183 [tomoyo_pp2mac[r->param.path2.operation]], in tomoyo_audit_path2_log()
199 [tomoyo_pnnn2mac[r->param.mkdev.operation]], in tomoyo_audit_mkdev_log()
214 const u8 type = r->param.path_number.operation; in tomoyo_audit_path_number_log()
241 * tomoyo_check_path_acl - Check permission for path operation.
258 if (acl->perm & (1 << r->param.path.operation)) { in tomoyo_check_path_acl()
268 * tomoyo_check_path_number_acl - Check permission for path number operation.
281 return (acl->perm & (1 << r->param.path_number.operation)) && in tomoyo_check_path_number_acl()
289 * tomoyo_check_path2_acl - Check permission for path path operation.
302 return (acl->perm & (1 << r->param.path2.operation)) && in tomoyo_check_path2_acl()
[all …]
|
| D | network.c | 27 u8 operation; member
288 const char *operation = tomoyo_read_token(param); in tomoyo_write_inet_network() local
294 if (tomoyo_permstr(operation, tomoyo_socket_keyword[type])) in tomoyo_write_inet_network()
333 const char *operation = tomoyo_read_token(param); in tomoyo_write_unix_network() local
339 if (tomoyo_permstr(operation, tomoyo_socket_keyword[type])) in tomoyo_write_unix_network()
358 * @operation: Name of socket operation.
365 const u8 operation, const char *address) in tomoyo_audit_net_log() argument
369 tomoyo_socket_keyword[operation], address); in tomoyo_audit_net_log()
394 r->param.inet_network.operation, buf); in tomoyo_audit_inet_log()
407 r->param.unix_network.operation, in tomoyo_audit_unix_log()
[all …]
|
| /Linux-v5.4/include/media/ |
| D | v4l2-device.h | 29 * @notify: notify operation called by some sub-devices.
231 * __v4l2_device_call_subdevs_p - Calls the specified operation for
240 * @f: operation function that will be called if @cond matches.
241 * The operation functions are defined in groups, according to
258 * __v4l2_device_call_subdevs - Calls the specified operation for
265 * @f: operation function that will be called if @cond matches.
266 * The operation functions are defined in groups, according to
284 * __v4l2_device_call_subdevs_until_err_p - Calls the specified operation for
293 * @f: operation function that will be called if @cond matches.
294 * The operation functions are defined in groups, according to
[all …]
|
| /Linux-v5.4/Documentation/core-api/ |
| D | atomic_ops.rst | 64 been set with this operation or set with another operation. A proper implicit
65 or explicit memory barrier is needed before the value set with the operation
186 Now, we move onto the atomic operation interfaces typically implemented with
209 atomic_t and return the new counter value after the operation is
214 the operation. It must be done such that all memory operations before
215 and after the atomic operation calls are strongly ordered with respect
216 to the atomic operation itself.
219 before and after the atomic operation.
245 the atomic operation::
251 provide explicit memory barrier semantics around the operation::
[all …]
|
| /Linux-v5.4/drivers/net/ethernet/qlogic/qed/ |
| D | qed_mcp.h | 309 * @return int - 0 - operation was successful.
322 * @return int - 0 - operation was successful.
335 * 0 - Operation was successul.
336 * -EBUSY - Operation failed
350 * 0 - Operation was successful.
351 * -EBUSY - Operation failed
366 * 0 - Operation was successful.
367 * -EBUSY - Operation failed
381 * 0 - Operation was successful.
382 * -EBUSY - Operation failed
[all …]
|
| /Linux-v5.4/include/crypto/ |
| D | akcipher.h | 25 * depending on the operation.
26 * After operation it will be updated with the actual size of the
29 * it will be updated to the size required for the operation.
55 * @sign: Function performs a sign operation as defined by public key
58 * operation
59 * @verify: Function performs a complete verify operation as defined by
62 * @encrypt: Function performs an encrypt operation as defined by public key
65 * operation
66 * @decrypt: Function performs a decrypt operation as defined by public key
69 * operation
[all …]
|
| /Linux-v5.4/drivers/staging/greybus/ |
| D | loopback.c | 54 struct gb_operation *operation; member
305 /* Maximum iterations for a given operation: 1-(2^32-1), 0 implies infinite */
374 struct gb_operation *operation; in gb_loopback_operation_sync() local
379 operation = gb_operation_create(gb->connection, type, request_size, in gb_loopback_operation_sync()
381 if (!operation) in gb_loopback_operation_sync()
385 memcpy(operation->request->payload, request, request_size); in gb_loopback_operation_sync()
387 ret = gb_operation_request_send_sync(operation); in gb_loopback_operation_sync()
390 "synchronous operation failed: %d\n", ret); in gb_loopback_operation_sync()
393 if (response_size == operation->response->payload_size) { in gb_loopback_operation_sync()
394 memcpy(response, operation->response->payload, in gb_loopback_operation_sync()
[all …]
|
| /Linux-v5.4/drivers/crypto/marvell/ |
| D | cesa.h | 136 * |-----------| 0x80 (inplace operation)
212 * @enc_p: input and output data pointers for a cipher operation
213 * @enc_len: cipher operation length
217 * @mac_digest: digest pointer and hash operation length
220 * Structure passed to the CESA engine to describe the crypto operation
235 * struct mv_cesa_blkcipher_op_ctx - cipher operation context
239 * Context associated to a cipher operation.
247 * struct mv_cesa_hash_op_ctx - hash or hmac operation context
251 * Context associated to an hash or hmac operation.
259 * struct mv_cesa_op_ctx - crypto operation context
[all …]
|
| /Linux-v5.4/drivers/dma/ppc4xx/ |
| D | adma.h | 88 * @pdest_page: P destination page for async validate operation
89 * @qdest_page: Q destination page for async validate operation
90 * @pdest: P dma addr for async validate operation
91 * @qdest: Q dma addr for async validate operation
124 * @group_head: first operation in a transaction
138 * @slots_per_op: number of slots per operation
139 * @descs_per_op: number of slot per P/Q operation see comment
174 #define PPC440SPE_DESC_RXOR123 8 /* CDB for RXOR123 operation */
175 #define PPC440SPE_DESC_RXOR124 9 /* CDB for RXOR124 operation */
176 #define PPC440SPE_DESC_RXOR125 10 /* CDB for RXOR125 operation */
[all …]
|
| /Linux-v5.4/net/netfilter/ |
| D | xt_ecn.c | 40 if (einfo->operation & XT_ECN_OP_MATCH_ECE) { in match_tcp()
50 if (einfo->operation & XT_ECN_OP_MATCH_CWR) { in match_tcp()
74 if (info->operation & XT_ECN_OP_MATCH_IP && !match_ip(skb, info)) in ecn_mt4()
77 if (info->operation & (XT_ECN_OP_MATCH_ECE | XT_ECN_OP_MATCH_CWR) && in ecn_mt4()
89 if (info->operation & XT_ECN_OP_MATCH_MASK) in ecn_mt_check4()
95 if (info->operation & (XT_ECN_OP_MATCH_ECE | XT_ECN_OP_MATCH_CWR) && in ecn_mt_check4()
116 if (info->operation & XT_ECN_OP_MATCH_IP && !match_ipv6(skb, info)) in ecn_mt6()
119 if (info->operation & (XT_ECN_OP_MATCH_ECE | XT_ECN_OP_MATCH_CWR) && in ecn_mt6()
131 if (info->operation & XT_ECN_OP_MATCH_MASK) in ecn_mt_check6()
137 if (info->operation & (XT_ECN_OP_MATCH_ECE | XT_ECN_OP_MATCH_CWR) && in ecn_mt_check6()
|
| /Linux-v5.4/crypto/ |
| D | algif_aead.c | 13 * up the TX SGL does not cause a crypto operation -- the data will only be
17 * During the processing of the recvmsg operation, the cipher request is
18 * allocated and prepared. As part of the recvmsg operation, the processed
21 * After the completion of the crypto operation, the RX SGL and the cipher
135 * cipher operation. When encrypting data, the receiving buffer is in _aead_recvmsg()
137 * encryption operation generates the tag. For decryption, the input in _aead_recvmsg()
147 * The cipher operation input data is reduced by the associated data in _aead_recvmsg()
152 /* Allocate cipher request for current operation. */ in _aead_recvmsg()
166 * allows AIO operation where the caller sent all data to be processed in _aead_recvmsg()
167 * and the AIO operation performs the operation on the different chunks in _aead_recvmsg()
[all …]
|
