Lines Matching refs:processor

9 Modern SoCs typically employ heterogeneous remote processor devices in
21 multimedia tasks from the main application processor.
29 hardware accessible only by the remote processor, reserving kernel-controlled
30 resources on behalf of the remote processor, etc..).
43 to the processor. To minimize the risks of rogue (or buggy) userland code
49 Every rpmsg device is a communication channel with a remote processor (thus
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
280 processor supports dynamic name service announcement messages.
283 is completely dynamic: the remote processor announces the existence of a