Documentation/staging/rpmsg.rst

2 Remote Processor Messaging (rpmsg) Framework
14 Modern SoCs typically employ heterogeneous remote processor devices in
26 multimedia tasks from the main application processor.
34 hardware accessible only by the remote processor, reserving kernel-controlled
35 resources on behalf of the remote processor, etc..).
48 to the processor. To minimize the risks of rogue (or buggy) userland code
54 Every rpmsg device is a communication channel with a remote processor (thus
73 sends a message across to the remote processor from the given endpoint.
81 one becomes available (i.e. until the remote processor consumes
93 sends a message across to the remote processor from a given endpoint,
99 The message will then be sent to the remote processor to which the
105 one becomes available (i.e. until the remote processor consumes
119 sends a message across to the remote processor, using the src and dst
124 The message will then be sent to the remote processor to which the
130 one becomes available (i.e. until the remote processor consumes
142 sends a message across to the remote processor from a given endpoint.
160 sends a message across to the remote processor from a given endpoint,
166 The message will then be sent to the remote processor to which the
182 sends a message across to the remote processor, using source and
187 The message will then be sent to the remote processor to which the
226 to the same remote processor their channel belongs to), an rx callback
332 processor supports dynamic name service announcement messages.
335 is completely dynamic: the remote processor announces the existence of a