Lines Matching refs:processor

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 on a given channel.
80 one becomes available (i.e. until the remote processor consumes
92 sends a message across to the remote processor on a given channel,
98 The message will then be sent to the remote processor to which the
103 one becomes available (i.e. until the remote processor consumes
117 sends a message across to the remote processor, using the src and dst
122 The message will then be sent to the remote processor to which the
127 one becomes available (i.e. until the remote processor consumes
139 sends a message across to the remote processor on a given channel.
156 sends a message across to the remote processor on a given channel,
162 The message will then be sent to the remote processor to which the
178 sends a message across to the remote processor, using source and
183 The message will then be sent to the remote processor to which the
222 to the same remote processor their channel belongs to), an rx callback
328 processor supports dynamic name service announcement messages.
331 is completely dynamic: the remote processor announces the existence of a