Lines Matching +full:inter +full:- +full:processor

12 For example, OMAP4 has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP,
17 A generic hwspinlock framework allows platform-independent drivers to use
22 This is necessary, for example, for Inter-processor communications:
23 on OMAP4, cpu-intensive multimedia tasks are offloaded by the host to the
26 To achieve fast message-based communications, a minimal kernel support
27 is needed to deliver messages arriving from a remote processor to the
32 module (remote processor directly places new messages in this shared data
35 A common hwspinlock interface makes it possible to have generic, platform-
56 Retrieve the global lock id for an OF phandle-based specific lock.
61 The function returns a lock id number on success, -EPROBE_DEFER if
71 Free a previously-assigned hwspinlock; returns 0 on success, or an
72 appropriate error code on failure (e.g. -EINVAL if the hwspinlock
83 (e.g. -EOPNOTSUPP if the bust operation is not defined for the specific
92 Lock a previously-assigned hwspinlock with a timeout limit (specified in
101 notably -ETIMEDOUT if the hwspinlock is still busy after timeout msecs).
108 Lock a previously-assigned hwspinlock with a timeout limit (specified in
116 notably -ETIMEDOUT if the hwspinlock is still busy after timeout msecs).
124 Lock a previously-assigned hwspinlock with a timeout limit (specified in
133 notably -ETIMEDOUT if the hwspinlock is still busy after timeout msecs).
141 Lock a previously-assigned hwspinlock with a timeout limit (specified in
146 or spinlock to avoid dead-lock, that will let user can do some time-consuming
150 notably -ETIMEDOUT if the hwspinlock is still busy after timeout msecs).
158 Lock a previously-assigned hwspinlock with a timeout limit (specified in
166 notably -ETIMEDOUT if the hwspinlock is still busy after timeout msecs).
175 Attempt to lock a previously-assigned hwspinlock, but immediately fail if
184 notably -EBUSY if the hwspinlock was already taken).
192 Attempt to lock a previously-assigned hwspinlock, but immediately fail if
200 notably -EBUSY if the hwspinlock was already taken).
208 Attempt to lock a previously-assigned hwspinlock, but immediately fail if
217 notably -EBUSY if the hwspinlock was already taken).
224 Attempt to lock a previously-assigned hwspinlock, but immediately fail if
228 or spinlock to avoid dead-lock, that will let user can do some time-consuming
232 notably -EBUSY if the hwspinlock was already taken).
239 Attempt to lock a previously-assigned hwspinlock, but immediately fail if
245 notably -EBUSY if the hwspinlock was already taken).
252 Unlock a previously-locked hwspinlock. Always succeed, and can be called
264 Unlock a previously-locked hwspinlock and enable local interrupts.
276 Unlock a previously-locked hwspinlock.
288 Unlock a previously-locked hwspinlock.
298 Unlock a previously-locked hwspinlock.
318 		* assign a specific hwspinlock id - this should be called early
329 			return -EBUSY;
356 To be called from the underlying platform-specific implementation, in
367 To be called from the underlying vendor-specific implementation, in order
386 	* struct hwspinlock_device - a device which usually spans numerous hwspinlocks
388 	* @ops: platform-specific hwspinlock handlers
405 	* struct hwspinlock - this struct represents a single hwspinlock instance
408 	* @priv: private data, owned by the underlying platform-specific hwspinlock drv
433 The ->trylock() callback should make a single attempt to take the lock, and
436 The ->unlock() callback releases the lock. It always succeed, and it, too,
439 The ->relax() callback is optional. It is called by hwspinlock core while
441 a delay between two successive invocations of ->trylock(). It may **not** sleep.