/linux/include/uapi/linux/ |
H A D | dma-buf.h | 39 * The synchronization provided via DMA_BUF_IOCTL_SYNC only provides cache 41 * accessing the memory at the same time. If synchronization with a GPU or 49 * synchronization, waiting for prior work to complete can be done via 51 * explicit synchronization, the client may have to wait on a sync_file or 52 * other synchronization primitive outside the scope of the DMA buffer API. 98 * synchronization model but still need to inter-operate with dma-buf. 112 * Unlike doing implicit synchronization via a GPU kernel driver's exec ioctl, 144 * sync_file into a dma-buf for the purposes of implicit synchronization 147 * which expect implicit synchronization such as OpenGL or most media
|
/linux/drivers/net/ethernet/xscale/ |
H A D | ixp46x_ts.h | 15 u32 ch_control; /* 0x40 Time Synchronization Channel Control */ 16 u32 ch_event; /* 0x44 Time Synchronization Channel Event */ 57 /* 0x40 Time Synchronization Channel Control Register Bits */ 61 /* 0x44 Time Synchronization Channel Event Register Bits */
|
/linux/arch/mips/include/asm/octeon/ |
H A D | cvmx-spi.h | 62 /** Called for calendar data synchronization */ 92 * @timeout: Timeout to wait for clock synchronization in seconds 101 * This routine restarts the SPI interface after it has lost synchronization 110 * @timeout: Timeout to wait for clock synchronization in seconds 212 * @timeout: Timeout to wait for clock synchronization in seconds 238 * Callback to perform calendar data synchronization
|
/linux/Documentation/devicetree/bindings/media/ |
H A D | renesas,vin.yaml | 18 with both external synchronization and BT.656 synchronization for the latter. 93 synchronization is selected. 99 synchronization is selected. 142 synchronization is selected. 148 synchronization is selected.
|
H A D | atmel,isc.yaml | 18 with both external synchronization and BT.656 synchronization for the latter.
|
/linux/Documentation/gpu/ |
H A D | drm-vm-bind-async.rst | 19 * ``syncobj``: A container that abstracts synchronization objects. The 20 synchronization objects can be either generic, like dma-fences or 22 underlying synchronization object. 30 * ``dma-fence``: A cross-driver synchronization object. A basic 35 * ``memory fence``: A synchronization object, different from a dma-fence. 175 synchronization part of the IOCTL is carried out: an asynchronous
|
/linux/drivers/media/platform/ti/omap3isp/ |
H A D | omap3isp.h | 33 * @hs_pol: Horizontal synchronization polarity 35 * @vs_pol: Vertical synchronization polarity 41 * @bt656: Data contain BT.656 embedded synchronization
|
/linux/Documentation/filesystems/iomap/ |
H A D | design.rst | 130 * **filesystem mapping lock**: This synchronization primitive is 137 synchronization primitives that iomap functions take while holding a 392 There are three categories of synchronization primitives, as far as 410 The upper level synchronization primitive, if any, remains held 411 while acquiring the lower level synchronization primitive. 415 synchronization here. 419 The upper level synchronization primitive, if any, remains held
|
/linux/arch/um/drivers/ |
H A D | chan_user.c | 170 os_info("winch_thread : failed to write synchronization byte, err = %d\n", in winch_thread() 209 * These are synchronization calls between various UML threads on the in winch_thread() 216 os_info("winch_thread : failed to read synchronization byte, err = %d\n", in winch_thread() 273 "synchronization byte\n"); in winch_tramp() 321 "synchronization byte, err = %d\n", errno); in register_winch()
|
/linux/drivers/firmware/tegra/ |
H A D | Kconfig | 11 keeps the content is synchronization between host CPU and remote 21 It needs HSP as the HW synchronization and notification module and
|
/linux/Documentation/devicetree/bindings/mailbox/ |
H A D | nvidia,tegra186-hsp.yaml | 7 title: NVIDIA Tegra Hardware Synchronization Primitives (HSP) 15 communicate together. It provides a set of hardware synchronization 17 communication (IPC) protocols can use hardware synchronization
|
/linux/include/uapi/drm/ |
H A D | panthor_drm.h | 212 * enum drm_panthor_sync_op_flags - Synchronization operation flags. 215 /** @DRM_PANTHOR_SYNC_OP_HANDLE_TYPE_MASK: Synchronization handle type mask. */ 218 /** @DRM_PANTHOR_SYNC_OP_HANDLE_TYPE_SYNCOBJ: Synchronization object type. */ 222 * @DRM_PANTHOR_SYNC_OP_HANDLE_TYPE_TIMELINE_SYNCOBJ: Timeline synchronization 235 * struct drm_panthor_sync_op - Synchronization operation. 238 /** @flags: Synchronization operation flags. Combination of DRM_PANTHOR_SYNC_OP values. */ 466 * VM (heap chunks, heap context, ring buffers, kernel synchronization objects, 535 * Just serves as a synchronization point on a VM queue. 575 * @syncs: Array of struct drm_panthor_sync_op synchronization 862 * synchronization point.
|
/linux/Documentation/core-api/ |
H A D | this_cpu_ops.rst | 26 without the typical synchronization overhead, but still provide some 32 synchronization is not necessary since we are dealing with per cpu 309 relaxed synchronization requirements for this_cpu operations. 313 share a cache-line but the relaxed synchronization is applied to 329 data within the same cache line are avoided. Also costly synchronization
|
H A D | dma-attributes.rst | 60 same synchronization operation on the CPU cache. CPU cache synchronization 63 DMA_ATTR_SKIP_CPU_SYNC allows platform code to skip synchronization of
|
/linux/drivers/infiniband/hw/ocrdma/ |
H A D | ocrdma.h | 254 /* provided synchronization to sgid table for 268 /* provide synchronization for av 325 spinlock_t cq_lock ____cacheline_aligned; /* provide synchronization 381 /* provide synchronization to multiple context(s) posting rqe */ 402 /* provide synchronization to multiple context(s) posting wqe, rqe */
|
/linux/Documentation/driver-api/ |
H A D | dma-buf.rst | 1 Buffer Sharing and Synchronization (dma-buf) 22 allowing implicit (kernel-ordered) synchronization of work to 251 that userspace uses for synchronization across engines or with the CPU, which 318 synchronization. Synchronization fences controlled by userspace must be used 324 faults. Specifically this means implicit synchronization will not be possible.
|
/linux/drivers/char/ |
H A D | bsr.c | 2 /* IBM POWER Barrier Synchronization Register Driver 23 synchronization across a large SMP machine. The hardware is exposed 31 own private synchronization device. 345 MODULE_DESCRIPTION("IBM POWER Barrier Synchronization Register Driver");
|
/linux/drivers/base/power/ |
H A D | common.c | 97 * Callers must ensure proper synchronization of this function with power 136 * Callers must ensure proper synchronization of this function with power 183 * Callers must ensure proper synchronization of this function with power 354 * Callers must ensure proper synchronization of this function with power 371 * Callers must ensure proper synchronization of this function with power
|
/linux/kernel/ |
H A D | async.c | 41 synchronization with the async_synchronize_full() function, before returning 192 * wait within a certain synchronization domain rather than globally. 293 * synchronization domain specified by @domain have been done. 307 * synchronization domain specified by @domain submitted prior to @cookie
|
/linux/kernel/rcu/ |
H A D | sync.c | 36 * @rhp: Pointer to rcu_head in rcu_sync structure to use for synchronization 92 * @rsp: Pointer to rcu_sync structure to use for synchronization 144 * @rsp: Pointer to rcu_sync structure to use for synchronization
|
/linux/arch/mips/kernel/ |
H A D | sync-r4k.c | 137 pr_info("Counter synchronization [CPU#%d -> CPU#%u]: passed\n", in check_counter_sync_source() 143 pr_info("Counter synchronization [CPU#%d -> CPU#%u]:\n", in check_counter_sync_source() 182 /* Kick the control CPU into the counter synchronization function */ in synchronise_count_slave()
|
/linux/drivers/irqchip/ |
H A D | irq-riscv-imsic-state.h | 33 /* Local dirty bitmap for synchronization */ 37 /* Local timer for synchronization */
|
/linux/include/linux/ |
H A D | console.h | 382 * on the console ownership for synchronization. 398 * The console ownership handling is necessary for synchronization 420 * NBCON callback to begin synchronization with driver code. 427 * use whatever synchronization mechanism the driver is using for 431 * synchronization method required by the driver. 434 * may be using a synchronization mechanism that already takes 447 * NBCON callback to finish synchronization with driver code.
|
/linux/tools/memory-model/scripts/ |
H A D | runlitmus.sh | 10 # But in this case, litmus tests using complex synchronization (such as 62 # Don't run on litmus tests with complex synchronization
|
/linux/include/linux/fsl/ |
H A D | ftm.h | 12 #define FTM_SYNC 0x58 /* Synchronization */ 25 #define FTM_SYNCONF 0x8C /* Synchronization Configuration */
|