Home
last modified time | relevance | path

Searched full:synchronization (Results 1 – 25 of 583) sorted by relevance

12345678910>>...24

/linux/Documentation/networking/
H A Dnetdevices.rst212 struct net_device synchronization rules
215 Synchronization: rtnl_lock() semaphore. In addition, netdev instance
220 Synchronization: rtnl_lock() semaphore. In addition, netdev instance
226 Synchronization: rtnl_lock() semaphore.
233 Synchronization: rtnl_lock() semaphore. In addition, netdev instance
241 Synchronization: rtnl_lock() semaphore. In addition, netdev instance
249 Synchronization: rtnl_lock() semaphore. In addition, netdev instance
257 Synchronization: rtnl_lock() semaphore. In addition, netdev instance
262 Synchronization: RCU (can be called concurrently with the stats
267 Synchronization: __netif_tx_lock spinlock.
[all …]
/linux/include/uapi/linux/
H A Ddma-buf.h40 * The synchronization provided via DMA_BUF_IOCTL_SYNC only provides cache
42 * accessing the memory at the same time. If synchronization with a GPU or
50 * synchronization, waiting for prior work to complete can be done via
52 * explicit synchronization, the client may have to wait on a sync_file or
53 * other synchronization primitive outside the scope of the DMA buffer API.
99 * synchronization model but still need to inter-operate with dma-buf.
113 * Unlike doing implicit synchronization via a GPU kernel driver's exec ioctl,
145 * sync_file into a dma-buf for the purposes of implicit synchronization
148 * which expect implicit synchronization such as OpenGL or most media
/linux/drivers/dma-buf/
H A DKconfig5 bool "Explicit Synchronization Framework"
9 The Sync File Framework adds explicit synchronization via
11 userspace via Sync File fds for synchronization between drivers via
27 synchronization. Useful when there is no hardware primitive backing
28 the synchronization.
/linux/drivers/net/ethernet/xscale/
H A Dixp46x_ts.h15 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/Documentation/devicetree/bindings/media/
H A Drenesas,vin.yaml18 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 Datmel,isc.yaml18 with both external synchronization and BT.656 synchronization for the latter.
/linux/Documentation/gpu/
H A Ddrm-vm-bind-async.rst19 * ``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 Domap3isp.h33 * @hs_pol: Horizontal synchronization polarity
35 * @vs_pol: Vertical synchronization polarity
41 * @bt656: Data contain BT.656 embedded synchronization
/linux/arch/um/drivers/
H A Dchan_user.c170 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/Documentation/devicetree/bindings/mailbox/
H A Dnvidia,tegra186-hsp.yaml7 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/drivers/char/
H A Dbsr.c2 /* IBM POWER Barrier Synchronization Register Driver
23 synchronization across a large SMP machine. The hardware is exposed
31 own private synchronization device.
344 MODULE_DESCRIPTION("IBM POWER Barrier Synchronization Register Driver");
/linux/drivers/base/power/
H A Dcommon.c97 * Callers must ensure proper synchronization of this function with power
139 * Callers must ensure proper synchronization of this function with power
186 * Callers must ensure proper synchronization of this function with power
357 * Callers must ensure proper synchronization of this function with power
374 * Callers must ensure proper synchronization of this function with power
/linux/kernel/
H A Dasync.c41 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/include/linux/
H A Dieee80211-mesh.h141 * @meshconf_synch: Synchronization Method Identifier
233 * enum ieee80211_mesh_sync_method - mesh synchronization method identifier
235 * @IEEE80211_SYNC_METHOD_NEIGHBOR_OFFSET: the default synchronization method
236 * @IEEE80211_SYNC_METHOD_VENDOR: a vendor specific synchronization method
H A Dconsole.h386 * on the console ownership for synchronization.
402 * The console ownership handling is necessary for synchronization
424 * NBCON callback to begin synchronization with driver code.
431 * use whatever synchronization mechanism the driver is using for
435 * synchronization method required by the driver.
438 * may be using a synchronization mechanism that already takes
451 * NBCON callback to finish synchronization with driver code.
H A Dasync.h65 * wait within a certain synchronization domain rather than globally.
107 * wait within a certain synchronization domain rather than globally.
/linux/kernel/rcu/
H A Dsync.c36 * @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 Dsync-r4k.c137 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 Dirq-riscv-imsic-state.h34 /* Local dirty bitmap for synchronization */
38 /* Local timer for synchronization */
/linux/tools/memory-model/scripts/
H A Drunlitmus.sh10 # 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 Dftm.h12 #define FTM_SYNC 0x58 /* Synchronization */
25 #define FTM_SYNCONF 0x8C /* Synchronization Configuration */
/linux/tools/testing/selftests/namespaces/
H A Dnsid_test.c92 /* Create a pipe for synchronization */ in TEST_F()
198 /* Create a pipe for synchronization */ in TEST_F()
304 /* Create a pipe for synchronization */ in TEST_F()
410 /* Create a pipe for synchronization */ in TEST_F()
516 /* Create a pipe for synchronization */ in TEST_F()
628 /* Create a pipe for synchronization */ in TEST_F()
748 /* Create a pipe for synchronization */ in TEST_F()
899 /* Create a pipe for synchronization */ in TEST_F()
/linux/Documentation/driver-api/soundwire/
H A Derror_handling.rst7 errors. Examples of this design can be found in the synchronization
55 possible in a single segment setup, but this can lead to synchronization
/linux/arch/arm/mm/
H A Dtlb-v6.S58 mcr p15, 0, ip, c7, c10, 4 @ data synchronization barrier
87 mcr p15, 0, r2, c7, c10, 4 @ data synchronization barrier
/linux/drivers/ptp/
H A DKconfig18 be used to achieve synchronization within a few dozen
21 synchronization to within a few hundred nanoseconds.
264 synchronization. It also supports periodic output signal (e.g. PPS)

12345678910>>...24