Home
last modified time | relevance | path

Searched full:holding (Results 1 – 25 of 2682) sorted by relevance

12345678910>>...108

/kernel/linux/linux-6.6/tools/memory-model/Documentation/
Dlocking.txt5 CPU holding a given lock sees any changes previously seen or made by any
18 Any CPU holding a given lock sees any changes previously seen
21 Note that this statement is a bit stronger than "Any CPU holding a
23 previously holding this same lock". For example, consider the following
53 The converse to the basic rule also holds: Any CPU holding a given
143 In short, if you access a lock-protected variable without holding the
148 Ordering Provided by a Lock to CPUs Not Holding That Lock
152 seen as ordered by CPUs not holding that lock. Consider this example:
184 Ordering can be extended to CPUs not holding the lock by careful use
254 CPU0() sets it to "1" while holding the lock, and CPU1() emulates the
[all …]
/kernel/linux/linux-6.6/fs/jffs2/
DREADME.Locking25 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
/kernel/linux/linux-5.10/fs/jffs2/
DREADME.Locking25 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
/kernel/linux/linux-6.6/arch/microblaze/lib/
Dmemcpy.c85 /* Load the holding buffer */ in memcpy()
94 /* Load the holding buffer */ in memcpy()
111 /* Load the holding buffer */ in memcpy()
120 /* Load the holding buffer */ in memcpy()
137 /* Load the holding buffer */ in memcpy()
146 /* Load the holding buffer */ in memcpy()
Dmemmove.c96 /* Load the holding buffer */ in memmove()
105 /* Load the holding buffer */ in memmove()
123 /* Load the holding buffer */ in memmove()
132 /* Load the holding buffer */ in memmove()
150 /* Load the holding buffer */ in memmove()
159 /* Load the holding buffer */ in memmove()
/kernel/linux/linux-5.10/sound/soc/atmel/
Dmchp-i2s-mcc.c44 #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 …]
/kernel/linux/linux-5.10/drivers/i2c/busses/
Di2c-at91.h42 #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 */
/kernel/linux/linux-6.6/drivers/i2c/busses/
Di2c-at91.h41 #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 */
/kernel/linux/linux-5.10/arch/microblaze/lib/
Dmemcpy.c96 /* 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()
Dmemmove.c118 /* 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()
/kernel/linux/linux-5.10/drivers/net/dsa/
Dmt7530.h617 /* 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 …]
/kernel/linux/linux-6.6/drivers/gpu/drm/radeon/
Dradeon_ring.c55 * @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 …]
/kernel/linux/linux-5.10/drivers/gpu/drm/radeon/
Dradeon_ring.c56 * @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
195 * @ring: radeon_ring structure holding ring information
210 * @ring: radeon_ring structure holding ring information
222 * @ring: radeon_ring structure holding ring information
235 * @ring: radeon_ring structure holding ring information
249 * @ring: radeon_ring structure holding ring information
[all …]
/kernel/linux/linux-5.10/drivers/block/paride/
DTransition-notes63 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
/kernel/linux/linux-6.6/include/linux/
Drcu_segcblist.h75 * | rcuc kthread, without holding nocb_lock. |
83 * | rcuc kthread, while holding nocb_lock. Waking up CB and GP kthreads, |
101 * | with rcu_core(), holding | | |
114 * | Kthreads handle callbacks holding nocb_lock, local rcu_core() stops |
131 * | CB/GP kthreads handle callbacks holding nocb_lock, local rcu_core() |
143 * | CB/GP kthreads handle callbacks holding nocb_lock, local rcu_core() |
157 * | holding nocb_lock. Wake up CB and GP kthreads if necessary. Disable |
187 * | rcuc kthread, while holding nocb_lock. Forbid nocb_timer to be armed. |
196 * | rcuc kthread, without holding nocb_lock. |
Diocontext.h41 * 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
/kernel/linux/linux-6.6/sound/soc/atmel/
Dmchp-i2s-mcc.c45 #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 …]
/kernel/linux/linux-5.10/drivers/pinctrl/qcom/
Dpinctrl-msm.h32 * @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.
/kernel/linux/linux-5.10/include/linux/
Diocontext.h41 * 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
/kernel/linux/linux-6.6/drivers/net/dsa/
Dmt7530.h699 /* struct mt7530_port - This is the main data structure for holding the state
731 /* struct mt753x_info - This is the main data structure for holding the specific
733 * @sw_setup: Holding the handler to a device initialization
734 * @phy_read_c22: Holding the way reading PHY port using C22
735 * @phy_write_c22: Holding the way writing PHY port using C22
736 * @phy_read_c45: Holding the way reading PHY port using C45
737 * @phy_write_c45: Holding the way writing PHY port using C45
738 * @pad_setup: Holding the way setting up the bus pad for a certain
742 * @mac_port_validate: Holding the way to set addition validate type for a
744 * @mac_port_config: Holding the way setting up the PHY attribute to a
[all …]
/kernel/linux/linux-6.6/drivers/ipack/devices/
Dscc2698.h26 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) */
/kernel/linux/linux-5.10/drivers/ipack/devices/
Dscc2698.h26 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) */
/kernel/linux/linux-5.10/Documentation/driver-api/
Dio-mapping.rst43 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.
/kernel/linux/linux-6.6/Documentation/locking/
Drobust-futex-ABI.rst11 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.
/kernel/linux/linux-5.10/Documentation/locking/
Drobust-futex-ABI.rst11 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.

12345678910>>...108