Searched refs:updater (Results 1 – 10 of 10) sorted by relevance
| /Linux-v4.19/Documentation/driver-api/dmaengine/ |
| D | pxa_dma.rst | 51 | desc-sg[0] | ... | desc-sg[last] | status updater | finisher/linker |
60 - status updater
109 d) Transfers completion updater
112 descriptor of a transfer, the "status updater", will write the latest
127 - reading the physical channel last updater mark
134 updater mark.
|
| /Linux-v4.19/drivers/dma/ |
| D | pxa_dma.c | 568 struct pxad_desc_hw *updater = in set_updater_desc() local
572 updater->ddadr = DDADR_STOP; in set_updater_desc()
573 updater->dsadr = dma; in set_updater_desc()
574 updater->dtadr = dma + 8; in set_updater_desc()
575 updater->dcmd = PXA_DCMD_WIDTH4 | PXA_DCMD_BURST32 | in set_updater_desc()
578 updater->dcmd |= PXA_DCMD_ENDIRQEN; in set_updater_desc()
586 struct pxad_desc_hw *updater = in is_desc_completed() local
589 return updater->dtadr != (updater->dsadr + 8); in is_desc_completed()
|
| /Linux-v4.19/Documentation/RCU/ |
| D | rcu_dereference.txt | 205 void updater(void)
240 but you should not be. After all, the updater might have been invoked
258 void updater(void)
321 void updater(void)
|
| D | whatisRCU.txt | 69 updater to perform the removal phase immediately, and to defer the
94 prevent an updater from deleting the data structure out from under them.
105 In the three-step procedure shown above, the updater is performing both
164 Marks the end of updater code and the beginning of reclaimer
221 The updater uses this function to assign a new value to an
223 in value from the updater to the reader. This function returns
296 reader, updater, and reclaimer.
309 | updater |<---------------------+ |
433 This primitive protects concurrent readers from the updater,
521 RCU distinction between updater, namely foo_update_a(), and reclaimer,
|
| D | lockdep.txt | 84 from taking place. If the above statement was invoked only from updater
|
| D | rcu.txt | 27 o How can the updater tell when a grace period has completed
|
| D | checklist.txt | 215 7. If the updater uses call_rcu() or synchronize_rcu(), then the
217 rcu_read_unlock(). If the updater uses call_rcu_bh() or
220 updater uses call_rcu_sched() or synchronize_sched(), then
223 If the updater uses synchronize_srcu() or call_srcu(), then
|
| D | RTFP.txt | 203 between memory barriers and read-side traversal order: If the updater
205 order, the updater need only execute a memory-barrier instruction,
206 but if in the same direction, the updater needs to wait for a grace
2641 If the updater is making changes in the opposite direction from
2642 the read-side traveral order, the updater need only execute a
2644 updater needs to wait for a grace period between the individual
|
| D | rcubarrier.txt | 22 pre-existing readers have completed. An updater wishing to delete an
|
| /Linux-v4.19/Documentation/sound/kernel-api/ |
| D | writing-an-alsa-driver.rst | 2157 /* call updater, unlock before it */
2210 /* call updater */
|
