Lines Matching refs:should

36       Note: to use this function you should already have a valid rproc
96       This function should be used by rproc implementations during
99       implementations should then call rproc_add() to complete
128       This function should be called when the platform specific rproc
129       implementation decides to remove the rproc device. it should
134       last refcount should be decremented by calling rproc_put().
141       platform specific rproc implementation. This should not be called from a
147 These callbacks should be provided by platform-specific remoteproc
162 Every remoteproc implementation should at least provide the ->start and ->stop
164 should be provided as well.
166 The ->start() handler takes an rproc handle and should then power on the
170 On success, 0 should be returned, and on failure, an appropriate error code.
176 where new message was placed in. Implementations should interrupt the remote
200 requires before it should be powered on, such as allocation of physically
220  * contains a version number (should we need to change this format in the
241  * this header, and it should be parsed according to the resource type.
252 the host should provide back its details (e.g. address of an allocated
291 The firmware should provide remoteproc information about virtio devices
293 should specify the virtio device id (as in virtio_ids.h), virtio features,