Lines Matching refs:processor

8 Modern SoCs typically have heterogeneous remote processor devices in asymmetric
29 existing virtio drivers with remote processor backends at a minimal development
39 Boot a remote processor (i.e. load its firmware, power it on, ...).
41 If the remote processor is already powered on, this function immediately
54 Power off a remote processor (previously booted with rproc_boot()).
76 the remote processor's refcount, so always use rproc_put() to
91 	/* let's power on and boot our remote processor */
100 	 * our remote processor is now powered on... give it some work
116 Allocate a new remote processor handle, but don't register
118 name of this remote processor, platform-specific ops handlers,
123 initialization of the remote processor.
127 the registration of the remote processor.
155 a new remote processor device is probed.
163 of registering this remote processor, additional virtio drivers might get
226 processor and let it know it has pending messages. Notifying remote processors
244 if the remote processor is accessing memory directly).
249 The resource table contains system resources that the remote processor
257 or configurations by the remote processor, such as trace buffers and
314    *		    the remote processor will be writing logs.
351 When a new remote processor is registered, the remoteproc framework
354 of any type (a single remote processor can also easily support several