Lines Matching refs:it
7 of operating system, whether it's Linux or any other flavor of real-time OS.
25 remoteproc will add those devices. This makes it possible to reuse the
32 - Boot a remote processor (i.e. load its firmware, power it on, ...).
51 rproc_shutdown() returns, and users can still use it with a subsequent
67 * something went wrong. handle it and leave.
72 * our remote processor is now powered on... give it some work
75 /* let's shut it down now */
85 it yet. Required parameters are the underlying device, the
97 Note: _never_ directly deallocate @rproc, even if it was not registered
108 - Register @rproc with the remoteproc framework, after it has been
123 implementation decides to remove the rproc device. it should
146 * @start: power on the device and boot it
161 device and boot it (use rproc->priv to access platform-specific private data).
171 processor and let it know it has pending messages. Notifying remote processors
172 the exact virtqueue index to look in is optional: it is easy (and not
179 it is quite expected that other platforms/devices which we'd want to
194 requires before it should be powered on, such as allocation of physically
235 * this header, and it should be parsed according to the resource type.
266 * please update it as needed.
286 that it supports, and their configurations: a RSC_VDEV resource entry
292 it supports. A firmware may support any number of virtio devices, and
299 rpmsg channels; read more about it in rpmsg.txt).