Lines Matching refs:processor

5 Modern SoCs typically have heterogeneous remote processor devices in asymmetric
26 existing virtio drivers with remote processor backends at a minimal development
32     - Boot a remote processor (i.e. load its firmware, power it on, ...).
33       If the remote processor is already powered on, this function immediately
42     - Power off a remote processor (previously booted with rproc_boot()).
57       the remote processor's refcount, so always use rproc_put() to
69 	/* let's power on and boot our remote processor */
78 	 * our remote processor is now powered on... give it some work
90     - Allocate a new remote processor handle, but don't register
92       name of this remote processor, platform-specific ops handlers,
97       initialization of the remote processor.
100       the registration of the remote processor.
117       a new remote processor device is probed.
123       of registering this remote processor, additional virtio drivers might get
177 processor and let it know it has pending messages. Notifying remote processors
194 if the remote processor is accessing memory directly).
199 The resource table contains system resources that the remote processor
207 or configurations by the remote processor, such as trace buffers and
264  *		    the remote processor will be writing logs.
296 When a new remote processor is registered, the remoteproc framework
299 of any type (a single remote processor can also easily support several