Lines Matching refs:and

3 Note: this document describes the rpmsg bus and how to write rpmsg drivers.
14 OMAP4, for example, has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP.
16 and each of the other three cores (two M3 cores and a DSP) is running
19 Typically AMP remote processors employ dedicated DSP codecs and multimedia
20 hardware accelerators, and therefore are often used to offload CPU-intensive
38 system's physical memory and other sensitive hardware resources (e.g. on
39 OMAP4, remote cores and hardware accelerators may have direct access to the
44 exploiting remote bugs, and by that taking over the system, it is often
46 it can send messages on, and if possible, minimize how much control
51 and have a local ("source") rpmsg address, and remote ("destination") rpmsg
66      and its length (in bytes). The message will be sent on the specified
67      channel, i.e. its source and destination address fields will be
68      set to the channel's src and dst addresses.
72      a tx buffer and puts it back on virtio's used descriptor ring),
76      Returns 0 on success and an appropriate error value on failure.
82      its length (in bytes), and an explicit destination address.
84      channel belongs, using the channel's src address, and the user-provided
89      a tx buffer and puts it back on virtio's used descriptor ring),
93      Returns 0 on success and an appropriate error value on failure.
97    - sends a message across to the remote processor, using the src and dst
100      its length (in bytes), and explicit source and destination addresses.
102      channel belongs, but the channel's src and dst addresses will be
103      ignored (and the user-provided addresses will be used instead).
107      a tx buffer and puts it back on virtio's used descriptor ring),
111      Returns 0 on success and an appropriate error value on failure.
116      and its length (in bytes). The message will be sent on the specified
117      channel, i.e. its source and destination address fields will be
118      set to the channel's src and dst addresses.
123      Returns 0 on success and an appropriate error value on failure.
129      its length (in bytes), and an explicit destination address.
131      channel belongs, using the channel's src address, and the user-provided
137      Returns 0 on success and an appropriate error value on failure.
141    - sends a message across to the remote processor, using source and
144      its length (in bytes), and explicit source and destination addresses.
146      channel belongs, but the channel's src and dst addresses will be
147      ignored (and the user-provided addresses will be used instead).
152      Returns 0 on success and an appropriate error value on failure.
161      This function allows drivers to create such an endpoint, and by that,
162      bind a callback, and possibly some private data too, to an rpmsg address
171      endpoint, their rx callback is bound to their rpmsg address, and when
177      additional rpmsg addresses, and bind them to different rx callbacks.
182      rx callback is invoked), and an address they want to bind with the
196      ->probe() and ->remove() functions, an rx callback, and an id_table
203      Returns 0 on success, and an appropriate error value on failure.
209 on probe(), and whenever it receives an incoming message, it dumps its
271 Note: a similar sample which can be built and loaded can be found
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.