Home
last modified time | relevance | path

Searched full:operation (Results 1 – 25 of 4215) sorted by relevance

12345678910>>...169

/kernel/linux/linux-5.10/drivers/greybus/
Doperation.c22 /* 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 …]
Dgreybus_trace.h71 * 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 …]
/kernel/linux/linux-5.10/include/linux/
Dccp.h45 * 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 …]
/kernel/linux/linux-5.10/include/linux/greybus/
Doperation.h25 * 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 …]
/kernel/linux/linux-5.10/drivers/acpi/pmic/
DKconfig4 bool "PMIC (Power Management Integrated Circuit) operation region support"
6 Select this option to enable support for ACPI operation
7 region of the PMIC chip. The operation region can be used
14 bool "ACPI operation region support for Bay Trail Crystal Cove PMIC"
17 This config adds ACPI operation region support for the Bay Trail
21 bool "ACPI operation region support for Cherry Trail Crystal Cove PMIC"
24 This config adds ACPI operation region support for the Cherry Trail
28 bool "ACPI operation region support for XPower AXP288 PMIC"
31 This config adds ACPI operation region support for XPower AXP288 PMIC.
34 bool "ACPI operation region support for BXT WhiskeyCove PMIC"
[all …]
/kernel/linux/linux-5.10/Documentation/filesystems/caching/
Doperations.rst13 (*) 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.
73 There are a number of parameters that can be set in the operation record's flag
77 (1) The operation may be done synchronously (FSCACHE_OP_MYTHREAD). A thread
78 may decide it wants to handle an operation itself without deferring it to
88 before submitting the operation, and the operating thread must wait for it
[all …]
/kernel/linux/linux-5.10/sound/soc/qcom/qdsp6/
Dq6dsp-errno.h7 /* 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 …]
/kernel/liteos_a/fs/vfs/
DBUILD.gn39 "operation/fullpath.c",
40 "operation/vfs_chattr.c",
41 "operation/vfs_check.c",
42 "operation/vfs_cloexec.c",
43 "operation/vfs_fallocate.c",
44 "operation/vfs_fallocate64.c",
45 "operation/vfs_fcntl.c",
46 "operation/vfs_force_umount.c",
47 "operation/vfs_init.c",
48 "operation/vfs_other.c",
[all …]
/kernel/linux/linux-5.10/include/trace/events/
Dblock.h67 * @rq: block IO operation request
69 * The block operation request @rq is being placed back into queue
104 * block_rq_complete - block IO operation completed by device driver
110 * of operation request has been completed by the device driver. If
182 * block_rq_insert - insert block operation request into queue
183 * @rq: block IO operation request
185 * Called immediately before block operation request @rq is inserted
186 * into queue @q. The fields in the operation request @rq struct can
188 * operation would access.
198 * block_rq_issue - issue pending block IO request operation to device driver
[all …]
/kernel/linux/linux-5.10/arch/arm/mm/
Dcache-uniphier.c31 /* 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 …]
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/arm64/
Darmv8-recommended.json213 "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 …]
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/arm64/hisilicon/hip08/
Dcore-imp-def.json105 …"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…
/kernel/linux/linux-5.10/tools/memory-model/Documentation/
Dcheatsheet.txt1 Prior Operation Subsequent Operation
8 Relaxed RMW operation Y Y Y Y
20 Key: Relaxed: A relaxed operation is either READ_ONCE(), WRITE_ONCE(),
21 a *_relaxed() RMW operation, an unsuccessful RMW
22 operation, a non-value-returning RMW operation such
30 a: Provides ordering given intervening RMW atomic operation
33 RMW: Atomic read-modify-write operation
/kernel/linux/linux-5.10/security/tomoyo/
Dfile.c169 [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 …]
/kernel/linux/linux-5.10/include/media/
Dv4l2-device.h29 * @notify: notify operation called by some sub-devices.
273 * __v4l2_device_call_subdevs_p - Calls the specified operation for
282 * @f: operation function that will be called if @cond matches.
283 * The operation functions are defined in groups, according to
300 * __v4l2_device_call_subdevs - Calls the specified operation for
307 * @f: operation function that will be called if @cond matches.
308 * The operation functions are defined in groups, according to
326 * __v4l2_device_call_subdevs_until_err_p - Calls the specified operation for
335 * @f: operation function that will be called if @cond matches.
336 * The operation functions are defined in groups, according to
[all …]
/kernel/linux/linux-5.10/Documentation/core-api/
Datomic_ops.rst64 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 …]
/kernel/linux/linux-5.10/Documentation/crypto/
Dasync-tx-api.rst17 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 …]
Duserspace-if.rst61 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 …]
/kernel/linux/linux-5.10/include/crypto/
Dakcipher.h25 * 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 …]
/kernel/linux/linux-5.10/drivers/staging/greybus/
Dloopback.c54 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 …]
/kernel/liteos_m/testsuites/unittest/xts/cmsis/
Dcmsis_sem_func_test.c49 * @tc.name : semaphore operation for creat when Semaphhore count = 1 and 0
65 * @tc.name : semaphore operation for creat when Semaphhore count = 10 and 1
81 * @tc.name : semaphore operation for creat when Semaphhore count = 0 and 10
97 * @tc.name : semaphore operation for creat when Semaphhore count = 0 and 0
113 * @tc.name : semaphore operation for creat when Semaphhore count = 1 and 1
129 * @tc.name : semaphore operation for creat when Semaphhore count = 10 and 10
145 * @tc.name : semaphore operation for creat when Semaphhore count = 0xFE and 0
161 * @tc.name : semaphore operation for creat when Semaphhore count = 0 and 0xFE
177 * @tc.name : semaphore operation for delete
192 * @tc.name : semaphore delete operation twice
[all …]
Dcmsis_timer_func_test.c76 * @tc.name : timer operation for creat with parameter osTimerOnce
94 * @tc.name : timer operation for creat with parameter osTimerPeriodic
112 * @tc.name : timer creat operation with NULL func and parameter osTimerOnce
129 * @tc.name : timer creat operation with NULL func and parameter osTimerPeriodic
146 * @tc.name : timer operation for invalid timer type
163 * @tc.name : timer operation for start with parameter osTimerOnce
182 * @tc.name : timer operation for start with parameter osTimerPeriodic
201 * @tc.name : timer operation for start with callback func and parameter osTimerOnce
226 * @tc.name : timer operation for start with callback func and parameter osTimerPeriodic
251 * @tc.name : timer start operation with ticks = 0 and parameter osTimerOnce
[all …]
/kernel/linux/linux-5.10/drivers/crypto/marvell/cesa/
Dcesa.h134 * |-----------| 0x80 (inplace operation)
210 * @enc_p: input and output data pointers for a cipher operation
211 * @enc_len: cipher operation length
215 * @mac_digest: digest pointer and hash operation length
218 * Structure passed to the CESA engine to describe the crypto operation
233 * struct mv_cesa_skcipher_op_ctx - cipher operation context
237 * Context associated to a cipher operation.
245 * struct mv_cesa_hash_op_ctx - hash or hmac operation context
249 * Context associated to an hash or hmac operation.
257 * struct mv_cesa_op_ctx - crypto operation context
[all …]
/kernel/linux/linux-5.10/drivers/net/ethernet/qlogic/qed/
Dqed_mcp.h317 * @return int - 0 - operation was successful.
330 * @return int - 0 - operation was successful.
343 * 0 - Operation was successul.
344 * -EBUSY - Operation failed
358 * 0 - Operation was successful.
359 * -EBUSY - Operation failed
374 * 0 - Operation was successful.
375 * -EBUSY - Operation failed
389 * 0 - Operation was successful.
390 * -EBUSY - Operation failed
[all …]
/kernel/linux/linux-5.10/drivers/dma/ppc4xx/
Dadma.h88 * @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 …]

12345678910>>...169