Searched full:holding (Results 1 – 25 of 1317) sorted by relevance
12345678910>>...53
/Linux-v5.15/drivers/infiniband/sw/rxe/ |
D | rxe_pool.h | 101 /* allocate an object from pool holding and not holding the pool lock */ 112 * pool's rb tree holding and not holding the pool_lock 123 * holding and not holding the pool_lock 134 * pool's rb tree holding and not holding pool_lock 144 /* remove elem from rb tree holding and not holding the pool_lock */ 153 /* lookup an indexed object from index holding and not holding the pool_lock. 160 /* lookup keyed object from key holding and not holding the pool_lock.
|
/Linux-v5.15/fs/jffs2/ |
D | README.Locking | 25 nodes to an inode may obsolete old ones, and by holding the alloc_sem 35 if the wbuf is currently holding any data is permitted, though. 87 may remove _obsolete_ nodes from the list while holding only the 88 erase_completion_lock. So you can walk the list only while holding the 90 long as the pointer you're holding is to a _valid_ node, not an 162 when updating such a object is necessary under holding read semaphore. 164 xdatum at first. But it retries this process with holding write-semaphore
|
/Linux-v5.15/drivers/i2c/busses/ |
D | i2c-at91.h | 41 #define AT91_TWI_THRCLR BIT(24) /* Transmit Holding Register Clear */ 42 #define AT91_TWI_RHRCLR BIT(25) /* Receive Holding Register Clear */ 63 #define AT91_TWI_RXRDY BIT(1) /* Receive Holding Register Ready */ 64 #define AT91_TWI_TXRDY BIT(2) /* Transmit Holding Register Ready */ 82 #define AT91_TWI_RHR 0x0030 /* Receive Holding Register */ 83 #define AT91_TWI_THR 0x0034 /* Transmit Holding Register */
|
/Linux-v5.15/arch/microblaze/lib/ |
D | memcpy.c | 98 /* Load the holding buffer */ in memcpy() 107 /* Load the holding buffer */ in memcpy() 124 /* Load the holding buffer */ in memcpy() 133 /* Load the holding buffer */ in memcpy() 150 /* Load the holding buffer */ in memcpy() 159 /* Load the holding buffer */ in memcpy()
|
D | memmove.c | 120 /* Load the holding buffer */ in memmove() 129 /* Load the holding buffer */ in memmove() 147 /* Load the holding buffer */ in memmove() 156 /* Load the holding buffer */ in memmove() 174 /* Load the holding buffer */ in memmove() 183 /* Load the holding buffer */ in memmove()
|
/Linux-v5.15/drivers/gpu/drm/radeon/ |
D | radeon_ring.c | 55 * @ring: radeon_ring structure holding ring information 77 * @ring: radeon_ring structure holding ring information 101 * @ring: radeon_ring structure holding ring information 136 * @ring: radeon_ring structure holding ring information 161 * @ring: radeon_ring structure holding ring information 193 * @ring: radeon_ring structure holding ring information 208 * @ring: radeon_ring structure holding ring information 221 * @ring: radeon_ring structure holding ring information 235 * @ring: radeon_ring structure holding ring information 249 * @ring: radeon_ring structure holding ring information [all …]
|
/Linux-v5.15/drivers/block/paride/ |
D | Transition-notes | 63 the thread was holding pd_lock and found pd_busy not set, which would 68 d) ps_tq_int() can enter the area only when the thread is holding 77 f) pi_wake_up() can enter the area only when the thread is holding 83 it is holding pd_lock. The only place within the area where we 97 the area are either after resetting ->claimed_cont to NULL while holding 118 can be killed. Indeed, we are not holding pd_lock and thus pd_busy is already
|
/Linux-v5.15/drivers/net/dsa/ |
D | mt7530.h | 700 /* struct mt7530_port - This is the main data structure for holding the state 744 /* struct mt753x_info - This is the main data structure for holding the specific 746 * @sw_setup: Holding the handler to a device initialization 747 * @phy_read: Holding the way reading PHY port 748 * @phy_write: Holding the way writing PHY port 749 * @pad_setup: Holding the way setting up the bus pad for a certain 753 * @mac_port_validate: Holding the way to set addition validate type for a 755 * @mac_port_get_state: Holding the way getting the MAC/PCS state for a certain 757 * @mac_port_config: Holding the way setting up the PHY attribute to a 759 * @mac_pcs_an_restart Holding the way restarting PCS autonegotiation for a [all …]
|
/Linux-v5.15/sound/soc/atmel/ |
D | mchp-i2s-mcc.c | 45 #define MCHP_I2SMCC_RHR 0x0030 /* Receiver Holding Register */ 46 #define MCHP_I2SMCC_THR 0x0034 /* Transmitter Holding Register */ 48 #define MCHP_I2SMCC_RHL0R 0x0040 /* Receiver Holding Left 0 Register */ 49 #define MCHP_I2SMCC_RHR0R 0x0044 /* Receiver Holding Right 0 Register */ 51 #define MCHP_I2SMCC_RHL1R 0x0048 /* Receiver Holding Left 1 Register */ 52 #define MCHP_I2SMCC_RHR1R 0x004C /* Receiver Holding Right 1 Register */ 54 #define MCHP_I2SMCC_RHL2R 0x0050 /* Receiver Holding Left 2 Register */ 55 #define MCHP_I2SMCC_RHR2R 0x0054 /* Receiver Holding Right 2 Register */ 57 #define MCHP_I2SMCC_RHL3R 0x0058 /* Receiver Holding Left 3 Register */ 58 #define MCHP_I2SMCC_RHR3R 0x005C /* Receiver Holding Right 3 Register */ [all …]
|
/Linux-v5.15/include/linux/ |
D | rcu_segcblist.h | 75 * | rcuc kthread, without holding nocb_lock. | 83 * | rcuc kthread, while holding nocb_lock. Waking up CB and GP kthreads, | 99 * | with rcu_core(), holding | | | 111 * | Kthreads handle callbacks holding nocb_lock, local rcu_core() stops | 127 * | CB/GP kthreads handle callbacks holding nocb_lock, local rcu_core() | 137 * | holding nocb_lock. Wake up CB and GP kthreads if necessary. Disable | 165 * | rcuc kthread, while holding nocb_lock. Forbid nocb_timer to be armed. | 174 * | rcuc kthread, without holding nocb_lock. |
|
D | iocontext.h | 41 * is called and be holding a reference to the associated io_context. 47 * Elevator is allowed to lookup icq using ioc_lookup_icq() while holding 62 * itself are also RCU managed and lookup can be performed holding only 69 * - Linking and unlinking icq's are performed while holding both ioc and q
|
/Linux-v5.15/drivers/pinctrl/qcom/ |
D | pinctrl-msm.h | 32 * @ctl_reg: Offset of the register holding control bits for this group. 33 * @io_reg: Offset of the register holding input/output bits for this group. 34 * @intr_cfg_reg: Offset of the register holding interrupt configuration bits. 35 * @intr_status_reg: Offset of the register holding the status bits for this group.
|
/Linux-v5.15/drivers/ipack/devices/ |
D | scc2698.h | 26 u8 d3, rhr; /* Receive holding register (R) */ 33 u8 d3, thr; /* Transmit holding register */ 51 u8 d3, rhra; /* Receive holding register (a) */ 59 u8 db, rhrb; /* Receive holding register (b) */ 69 u8 d3, thra; /* Transmit holding register (a) */ 77 u8 db, thrb; /* Transmit holding register (b) */
|
/Linux-v5.15/Documentation/locking/ |
D | robust-futex-ABI.rst | 11 The interesting data as to what futexes a thread is holding is kept on a 65 of the thread holding the lock in the bottom 30 bits. See further 88 specified 'offset'. Should a thread die while holding any such locks, 130 thread currently holding such a lock, if any, is marked with the threads 169 lock owner died holding the lock.
|
/Linux-v5.15/drivers/gpu/drm/amd/amdgpu/ |
D | amdgpu_ring.c | 55 * @ring: amdgpu_ring structure holding ring information 84 * @ring: amdgpu_ring structure holding ring information 100 * @ring: amdgpu_ring structure holding ring information 115 * @ring: amdgpu_ring structure holding ring information 140 * @ring: amdgpu_ring structure holding ring information 156 * @ring: amdgpu_ring structure holding ring information 279 * @ring: amdgpu_ring structure holding ring information
|
/Linux-v5.15/tools/memory-model/litmus-tests/ |
D | Z6.0+pooncelock+pooncelock+pombonce.litmus | 7 * processes each while holding a given lock will not necessarily be 8 * seen as ordered by a third process not holding that lock.
|
D | MP+porevlocks.litmus | 8 * In other words, when holding a given lock (or indeed after releasing a 10 * CPUs made while previously holding that lock, it is also guaranteed to
|
D | MP+polocks.litmus | 8 * In other words, when holding a given lock (or indeed after releasing a 10 * CPUs made while previously holding that lock, it is also guaranteed
|
/Linux-v5.15/Documentation/filesystems/ |
D | directory-locking.rst | 93 not contended, since any process blocked on it is not holding any locks. 96 By (3), any process holding a non-directory lock can only be 98 the process holding the "largest" such lock can always make progress, and 130 rename() responsible for that would be holding filesystem lock and new parent
|
/Linux-v5.15/arch/arm/mach-exynos/ |
D | headsmp.S | 15 * a "holding pen" into which all secondary cores are held until we're 31 * we've been released from the holding pen: secondary_stack
|
/Linux-v5.15/arch/arm/plat-versatile/ |
D | headsmp.S | 14 * This provides a "holding pen" into which all secondary cores are held 30 * we've been released from the holding pen: secondary_stack
|
/Linux-v5.15/fs/btrfs/ |
D | locking.h | 26 * When we COW a block we are holding the lock on the original block, 35 * still holding the lock on the original node we searched to, such as 46 * When splitting we will be holding a lock on the left/right node when
|
/Linux-v5.15/arch/arm/include/debug/ |
D | at91.S | 9 #define AT91_DBGU_THR (0x1c) /* Transmitter Holding Register */ 19 strb \rd, [\rx, #(AT91_DBGU_THR)] @ Write to Transmitter Holding Register
|
/Linux-v5.15/drivers/misc/vmw_vmci/ |
D | vmci_datagram.h | 21 * content is accessed while holding a spinlock. The pending datagram 24 * while holding the same spinlock as above.
|
/Linux-v5.15/arch/arm/mach-spear/ |
D | headsmp.S | 17 * a "holding pen" into which all secondary cores are held until we're 36 * we've been released from the holding pen: secondary_stack
|
12345678910>>...53