Searched full:holding (Results 1 – 25 of 1283) sorted by relevance
12345678910>>...52
| /Linux-v5.10/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.10/sound/soc/atmel/ |
| D | mchp-i2s-mcc.c | 44 #define MCHP_I2SMCC_RHR 0x0030 /* Receiver Holding Register */
45 #define MCHP_I2SMCC_THR 0x0034 /* Transmitter Holding Register */
47 #define MCHP_I2SMCC_RHL0R 0x0040 /* Receiver Holding Left 0 Register */
48 #define MCHP_I2SMCC_RHR0R 0x0044 /* Receiver Holding Right 0 Register */
50 #define MCHP_I2SMCC_RHL1R 0x0048 /* Receiver Holding Left 1 Register */
51 #define MCHP_I2SMCC_RHR1R 0x004C /* Receiver Holding Right 1 Register */
53 #define MCHP_I2SMCC_RHL2R 0x0050 /* Receiver Holding Left 2 Register */
54 #define MCHP_I2SMCC_RHR2R 0x0054 /* Receiver Holding Right 2 Register */
56 #define MCHP_I2SMCC_RHL3R 0x0058 /* Receiver Holding Left 3 Register */
57 #define MCHP_I2SMCC_RHR3R 0x005C /* Receiver Holding Right 3 Register */
[all …]
|
| /Linux-v5.10/arch/microblaze/lib/ |
| D | memcpy.c | 96 /* Load the holding buffer */ in memcpy()
105 /* Load the holding buffer */ in memcpy()
122 /* Load the holding buffer */ in memcpy()
131 /* Load the holding buffer */ in memcpy()
148 /* Load the holding buffer */ in memcpy()
157 /* Load the holding buffer */ in memcpy()
|
| D | memmove.c | 118 /* Load the holding buffer */ in memmove()
127 /* Load the holding buffer */ in memmove()
145 /* Load the holding buffer */ in memmove()
154 /* Load the holding buffer */ in memmove()
172 /* Load the holding buffer */ in memmove()
181 /* Load the holding buffer */ in memmove()
|
| /Linux-v5.10/drivers/i2c/busses/ |
| D | i2c-at91.h | 42 #define AT91_TWI_THRCLR BIT(24) /* Transmit Holding Register Clear */
43 #define AT91_TWI_RHRCLR BIT(25) /* Receive Holding Register Clear */
64 #define AT91_TWI_RXRDY BIT(1) /* Receive Holding Register Ready */
65 #define AT91_TWI_TXRDY BIT(2) /* Transmit Holding Register Ready */
83 #define AT91_TWI_RHR 0x0030 /* Receive Holding Register */
84 #define AT91_TWI_THR 0x0034 /* Transmit Holding Register */
|
| /Linux-v5.10/drivers/net/dsa/ |
| D | mt7530.h | 617 /* struct mt7530_port - This is the main data structure for holding the state
659 /* struct mt753x_info - This is the main data structure for holding the specific
661 * @sw_setup: Holding the handler to a device initialization
662 * @phy_read: Holding the way reading PHY port
663 * @phy_write: Holding the way writing PHY port
664 * @pad_setup: Holding the way setting up the bus pad for a certain
668 * @mac_port_validate: Holding the way to set addition validate type for a
670 * @mac_port_get_state: Holding the way getting the MAC/PCS state for a certain
672 * @mac_port_config: Holding the way setting up the PHY attribute to a
674 * @mac_pcs_an_restart Holding the way restarting PCS autonegotiation for a
[all …]
|
| /Linux-v5.10/drivers/gpu/drm/radeon/ |
| D | radeon_ring.c | 56 * @ring: radeon_ring structure holding ring information
78 * @ring: radeon_ring structure holding ring information
102 * @ring: radeon_ring structure holding ring information
137 * @ring: radeon_ring structure holding ring information
162 * @ring: radeon_ring structure holding ring information
194 * @ring: radeon_ring structure holding ring information
209 * @ring: radeon_ring structure holding ring information
221 * @ring: radeon_ring structure holding ring information
234 * @ring: radeon_ring structure holding ring information
248 * @ring: radeon_ring structure holding ring information
[all …]
|
| /Linux-v5.10/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.10/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.10/include/linux/ |
| 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.10/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.10/Documentation/driver-api/ |
| D | io-mapping.rst | 43 Note that the task may not sleep while holding this page
54 If you need to sleep while holding the lock, you can use the non-atomic
63 the task to sleep while holding the page mapped.
|
| /Linux-v5.10/include/trace/events/ |
| D | block.h | 67 * @q: queue holding operation
201 * @q: queue holding operation
216 * @q: queue holding operation
231 * @q: queue holding the block operation
270 * @q: queue holding the block operation
334 * @q: queue holding operation
350 * @q: queue holding operation
366 * @q: queue holding operation
565 * @q: queue holding the operation
608 * @q: queue holding the operation
|
| /Linux-v5.10/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.10/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+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
|
| 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
|
| /Linux-v5.10/arch/arm/mach-prima2/ |
| D | headsmp.S | 13 * a "holding pen" into which all secondary cores are held until we're
28 * we've been released from the holding pen: secondary_stack
|
| /Linux-v5.10/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.10/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.10/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.10/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.10/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.10/drivers/gpu/drm/amd/amdgpu/ |
| D | amdgpu_ring.c | 56 * @ring: amdgpu_ring structure holding ring information
85 * @ring: amdgpu_ring structure holding ring information
100 * @ring: amdgpu_ring structure holding ring information
116 * @ring: amdgpu_ring structure holding ring information
141 * @ring: amdgpu_ring structure holding ring information
157 * @ring: amdgpu_ring structure holding ring information
280 * @ring: amdgpu_ring structure holding ring information
|
| /Linux-v5.10/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>>...52
