| /kernel/linux/linux-5.10/drivers/crypto/ccp/ |
| D | ccp-crypto-main.c | 77 /* Used for held command processing to determine state */
99 struct ccp_crypto_cmd *held = NULL, *tmp; in ccp_crypto_cmd_complete() local
106 /* Held cmds will be after the current cmd in the queue so start in ccp_crypto_cmd_complete()
113 held = tmp; in ccp_crypto_cmd_complete()
141 return held; in ccp_crypto_cmd_complete()
147 struct ccp_crypto_cmd *held, *next, *backlog; in ccp_crypto_complete() local
166 held = ccp_crypto_cmd_complete(crypto_cmd, &backlog); in ccp_crypto_complete()
183 while (held) { in ccp_crypto_complete()
187 held->cmd->flags |= CCP_CMD_MAY_BACKLOG; in ccp_crypto_complete()
188 ret = ccp_enqueue_cmd(held->cmd); in ccp_crypto_complete()
[all …]
|
| /kernel/linux/linux-6.6/drivers/crypto/ccp/ |
| D | ccp-crypto-main.c | 77 /* Used for held command processing to determine state */
92 struct ccp_crypto_cmd *held = NULL, *tmp; in ccp_crypto_cmd_complete() local
99 /* Held cmds will be after the current cmd in the queue so start in ccp_crypto_cmd_complete()
106 held = tmp; in ccp_crypto_cmd_complete()
134 return held; in ccp_crypto_cmd_complete()
140 struct ccp_crypto_cmd *held, *next, *backlog; in ccp_crypto_complete() local
159 held = ccp_crypto_cmd_complete(crypto_cmd, &backlog); in ccp_crypto_complete()
176 while (held) { in ccp_crypto_complete()
180 held->cmd->flags |= CCP_CMD_MAY_BACKLOG; in ccp_crypto_complete()
181 ret = ccp_enqueue_cmd(held->cmd); in ccp_crypto_complete()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-coresight-devices-tmc | 21 Description: (Read) Shows the value held by the TMC status register. The value
28 Description: (Read) Shows the value held by the TMC RAM Read Pointer register
37 Description: (Read) Shows the value held by the TMC RAM Write Pointer register
53 Description: (Read) Shows the value held by the TMC Control register. The value
60 Description: (Read) Shows the value held by the TMC Formatter and Flush Status
68 Description: (Read) Shows the value held by the TMC Formatter and Flush Control
76 Description: (Read) Shows the value held by the TMC Mode register, which
|
| D | sysfs-bus-coresight-devices-etb10 | 33 Description: (Read) Shows the value held by the ETB status register. The value
40 Description: (Read) Shows the value held by the ETB RAM Read Pointer register
49 Description: (Read) Shows the value held by the ETB RAM Write Pointer register
65 Description: (Read) Shows the value held by the ETB Control register. The value
72 Description: (Read) Shows the value held by the ETB Formatter and Flush Status
80 Description: (Read) Shows the value held by the ETB Formatter and Flush Control
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-bus-coresight-devices-tmc | 21 Description: (Read) Shows the value held by the TMC status register. The value
28 Description: (Read) Shows the value held by the TMC RAM Read Pointer register
37 Description: (Read) Shows the value held by the TMC RAM Write Pointer register
53 Description: (Read) Shows the value held by the TMC Control register. The value
60 Description: (Read) Shows the value held by the TMC Formatter and Flush Status
68 Description: (Read) Shows the value held by the TMC Formatter and Flush Control
76 Description: (Read) Shows the value held by the TMC Mode register, which
|
| D | sysfs-bus-coresight-devices-etb10 | 33 Description: (Read) Shows the value held by the ETB status register. The value
40 Description: (Read) Shows the value held by the ETB RAM Read Pointer register
49 Description: (Read) Shows the value held by the ETB RAM Write Pointer register
65 Description: (Read) Shows the value held by the ETB Control register. The value
72 Description: (Read) Shows the value held by the ETB Formatter and Flush Status
80 Description: (Read) Shows the value held by the ETB Formatter and Flush Control
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/powerpc/power10/ |
| D | pipeline.json | 10 …"BriefDescription": "Cycles in which the next-to-complete (NTC) instruction is held at dispatch fo…
75 …"BriefDescription": "Cycles in which the next-to-complete (NTC) instruction is held at dispatch be…
80 …"BriefDescription": "Cycles in which the next-to-complete (NTC) instruction is held at dispatch be…
100 "BriefDescription": "Cycles dispatch is held."
130 …"BriefDescription": "Cycles in which the next-to-complete (NTC) instruction is held at dispatch du…
210 …BriefDescription": "Cycles when dispatch was stalled for this thread because Fetch was being held."
215 …"BriefDescription": "Cycles in which the next-to-complete (NTC) instruction is held at dispatch be…
235 "BriefDescription": "Cycles dispatch is held for any other reason."
240 …"BriefDescription": "Cycles dispatch is held because the STF mapper/SRB was full. Includes GPR (co…
265 …"BriefDescription": "Cycles in which the next-to-complete (NTC) instruction is held at dispatch wh…
[all …]
|
| /kernel/linux/linux-6.6/Documentation/locking/ |
| D | robust-futex-ABI.rst | 9 futexes, for kernel assist of cleanup of held locks on task exit.
18 held robust_futexes begins, and
19 2) internal kernel code at exit, to handle any listed locks held
85 For each futex lock currently held by a thread, if it wants this
114 up locks held at the time of (a perhaps unexpectedly) exit.
121 still held by the departing thread, as described below.
125 lock structures for locks currently held by that thread should be on
128 A given futex lock structure in a user shared memory region may be held
133 When adding or removing a lock from its list of held locks, in order for
|
| /kernel/linux/linux-5.10/Documentation/locking/ |
| D | robust-futex-ABI.rst | 9 futexes, for kernel assist of cleanup of held locks on task exit.
18 held robust_futexes begins, and
19 2) internal kernel code at exit, to handle any listed locks held
85 For each futex lock currently held by a thread, if it wants this
114 up locks held at the time of (a perhaps unexpectedly) exit.
121 still held by the departing thread, as described below.
125 lock structures for locks currently held by that thread should be on
128 A given futex lock structure in a user shared memory region may be held
133 When adding or removing a lock from its list of held locks, in order for
|
| /kernel/linux/linux-6.6/drivers/media/rc/ |
| D | ite-cir.c | 175 * spinlock held */
516 /* set the carrier parameters; to be called with the spinlock held */
544 * held */
563 * with the device spinlock NOT HELD while waiting for the TX FIFO to get
570 /* put a byte to the TX fifo; this should be called with the spinlock held */
577 pulse is detected; this must be called with the device spinlock held */
589 /* disable the receiver; this must be called with the device spinlock held */
605 /* enable the receiver; this must be called with the device spinlock held */
621 * spinlock held */
630 * spinlock held */
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/remoteproc/ |
| D | qcom,wcnss-pil.yaml | 61 PX regulator to be held on behalf of the booting of the WCNSS core
65 MX regulator to be held on behalf of the booting of the WCNSS core.
69 CX regulator to be held on behalf of the booting of the WCNSS core.
129 Reference to the regulator to be held on behalf of the booting WCNSS
134 Reference to the regulator to be held on behalf of the booting WCNSS
139 Reference to the regulator to be held on behalf of the booting WCNSS
144 Reference to the regulator to be held on behalf of the booting WCNSS
|
| /kernel/linux/linux-5.10/drivers/infiniband/core/ |
| D | uverbs.h | 80 * struct ib_uverbs_device: One reference is held by the module and
85 * struct ib_uverbs_file: One reference is held by the VFS and
92 * One reference is held by the VFS and released when the file is closed.
93 * For asynchronous event files, another reference is held by the corresponding
142 * ucontext_lock held
149 * To access the uobjects list hw_destroy_rwsem must be held for write
150 * OR hw_destroy_rwsem held for read AND uobjects_lock held.
|
| /kernel/linux/linux-6.6/drivers/infiniband/core/ |
| D | uverbs.h | 80 * struct ib_uverbs_device: One reference is held by the module and
85 * struct ib_uverbs_file: One reference is held by the VFS and
92 * One reference is held by the VFS and released when the file is closed.
93 * For asynchronous event files, another reference is held by the corresponding
142 * ucontext_lock held
149 * To access the uobjects list hw_destroy_rwsem must be held for write
150 * OR hw_destroy_rwsem held for read AND uobjects_lock held.
|
| /kernel/linux/linux-6.6/Documentation/arch/s390/ |
| D | vfio-ap-locking.rst | 31 (matrix_dev->mdev_list). This lock must be held while reading from, writing to
47 lock must be held by the vfio_ap device driver while one or more AP adapters,
69 KVM guest. This lock must be held:
91 held in order to access the KVM pointer since it is set and cleared under the
95 resources, so only the matrix_dev->mdevs_lock needs to be held.
114 held in write mode when pqap_hook value is set, and in read mode when the
|
| /kernel/linux/linux-5.10/drivers/media/rc/ |
| D | ite-cir.c | 210 * spinlock held */
573 /* set the carrier parameters; to be called with the spinlock held */
603 * held */
624 * with the device spinlock NOT HELD while waiting for the TX FIFO to get
633 /* put a byte to the TX fifo; this should be called with the spinlock held */
640 pulse is detected; this must be called with the device spinlock held */
654 /* disable the receiver; this must be called with the device spinlock held */
672 /* enable the receiver; this must be called with the device spinlock held */
690 * spinlock held */
701 * spinlock held */
[all …]
|
| /kernel/linux/linux-5.10/Documentation/dev-tools/ |
| D | sparse.rst | 61 locking. These annotations tell sparse when a lock is held, with
64 __must_hold - The specified lock is held on function entry and exit.
66 __acquires - The specified lock is held on function exit, but not entry.
68 __releases - The specified lock is held on function entry, but not exit.
70 If the function enters and exits without the lock held, acquiring and
|
| /kernel/linux/linux-6.6/Documentation/dev-tools/ |
| D | sparse.rst | 61 locking. These annotations tell sparse when a lock is held, with
64 __must_hold - The specified lock is held on function entry and exit.
66 __acquires - The specified lock is held on function exit, but not entry.
68 __releases - The specified lock is held on function entry, but not exit.
70 If the function enters and exits without the lock held, acquiring and
|
| /kernel/linux/linux-5.10/fs/btrfs/ |
| D | locking.c | 42 * spinning semantics - the low-level rwlock is held so all other threads that
45 * blocking semantics - the low-level rwlock is not held but the counter
46 * denotes how many times the blocking lock was held;
85 * | - extent_buffer::rwlock is held
188 * Mark already held read lock as blocking. Can be nested in write lock by the
213 * Mark already held write lock as blocking.
245 * The rwlock is held upon exit.
364 * The rwlock is not held upon exit.
417 * The rwlock is held for write upon exit.
455 * Tasks blocked and waiting are woken, rwlock is not held upon exit.
[all …]
|
| /kernel/linux/linux-6.6/drivers/tty/serial/ |
| D | sunhv.c | 231 /* port->lock is not held. */
241 /* port->lock held by caller. */
247 /* port->lock is held by caller and interrupts are disabled. */
253 /* port->lock held by caller. */
259 /* port->lock held by caller. */
265 /* port->lock is not held. */
286 /* port->lock held by caller. */
291 /* port->lock is not held. */
311 /* port->lock is not held. */
317 /* port->lock is not held. */
[all …]
|
| /kernel/linux/linux-5.10/net/strparser/ |
| D | strparser.c | 36 /* Lower lock held */
63 /* Lower lock held */
88 /* Lower socket lock held */
344 /* Called with lock held on lower socket */
365 /* Lower sock lock held */
373 * the lock held here is bh_lock_sock. The two locks can be in strp_data_ready()
374 * held by different threads at the same time, but bh_lock_sock in strp_data_ready()
376 * lock is held. In this case, if the lock is held, queue work. in strp_data_ready()
481 /* Sock process lock held (lock_sock) */
506 * Note that strp_done is not called with the lower socket held.
|
| /kernel/linux/linux-5.10/drivers/tty/serial/ |
| D | sunhv.c | 233 /* port->lock is not held. */
243 /* port->lock held by caller. */
249 /* port->lock is held by caller and interrupts are disabled. */
255 /* port->lock held by caller. */
261 /* port->lock held by caller. */
267 /* port->lock is not held. */
288 /* port->lock held by caller. */
293 /* port->lock is not held. */
313 /* port->lock is not held. */
319 /* port->lock is not held. */
[all …]
|
| /kernel/linux/linux-6.6/net/strparser/ |
| D | strparser.c | 36 /* Lower lock held */
63 /* Lower lock held */
88 /* Lower socket lock held */
344 /* Called with lock held on lower socket */
371 /* Lower sock lock held */
379 * the lock held here is bh_lock_sock. The two locks can be in strp_data_ready()
380 * held by different threads at the same time, but bh_lock_sock in strp_data_ready()
382 * lock is held. In this case, if the lock is held, queue work. in strp_data_ready()
488 /* Sock process lock held (lock_sock) */
513 * Note that strp_done is not called with the lower socket held.
|
| /kernel/linux/linux-5.10/Documentation/leds/ |
| D | ledtrig-transient.rst | 12 features that require an on or off state to be held just once and then stay in
75 - state allows user to specify a transient state to be held for the specified
96 - transient state to be held. It has two values 0 or 1. 0 maps
98 held for the duration of the one shot timer and then the
128 held for the specified duration.
130 held for the specified duration.
|
| /kernel/linux/linux-6.6/Documentation/leds/ |
| D | ledtrig-transient.rst | 12 features that require an on or off state to be held just once and then stay in
75 - state allows user to specify a transient state to be held for the specified
96 - transient state to be held. It has two values 0 or 1. 0 maps
98 held for the duration of the one shot timer and then the
128 held for the specified duration.
130 held for the specified duration.
|
| /kernel/linux/linux-5.10/Documentation/filesystems/nfs/ |
| D | pnfs.rst | 22 LAYOUTCOMMIT), and for each lseg held within.
33 layout driver type. The device ids are held in a RCU cache (struct
35 mount. The entries (struct nfs4_deviceid) themselves are held across
51 level cache. Its reference is held over the lifetime of the deviceid
|