Lines Matching refs:remote

9 Modern SoCs typically employ heterogeneous remote processor devices in
19 Typically AMP remote processors employ dedicated DSP codecs and multimedia
23 These remote processors could also be used to control latency-sensitive
27 Users of those remote processors can either be userland apps (e.g. multimedia
28 frameworks talking with remote OMX components) or kernel drivers (controlling
29 hardware accessible only by the remote processor, reserving kernel-controlled
30 resources on behalf of the remote processor, etc..).
33 with remote processors available on the system. In turn, drivers could then
37 keep in mind that remote processors might have direct access to the
39 OMAP4, remote cores and hardware accelerators may have direct access to the
41 devices, hwspinlocks, etc..). Moreover, those remote processors might be
44 exploiting remote bugs, and by that taking over the system, it is often
49 Every rpmsg device is a communication channel with a remote processor (thus
51 and have a local ("source") rpmsg address, and remote ("destination") rpmsg
64    - sends a message across to the remote processor on a given channel.
71      one becomes available (i.e. until the remote processor consumes
79    - sends a message across to the remote processor on a given channel,
83      The message will then be sent to the remote processor to which the
88      one becomes available (i.e. until the remote processor consumes
97    - sends a message across to the remote processor, using the src and dst
101      The message will then be sent to the remote processor to which the
106      one becomes available (i.e. until the remote processor consumes
114    - sends a message across to the remote processor on a given channel.
126    - sends a message across to the remote processor on a given channel,
130      The message will then be sent to the remote processor to which the
141    - sends a message across to the remote processor, using source and
145      The message will then be sent to the remote processor to which the
180      to the same remote processor their channel belongs to), an rx callback
278 This is possible only with remote processors that have the VIRTIO_RPMSG_F_NS
279 virtio device feature set. This feature bit means that the remote
283 is completely dynamic: the remote processor announces the existence of a
284 remote rpmsg service by sending a name service message (which contains
285 the name and rpmsg addr of the remote service, see struct rpmsg_ns_msg).
288 creates and registers an rpmsg channel (which represents the remote service).
290 by the bus, and can then start sending messages to the remote service.