Lines Matching refs:rproc
31 int rproc_boot(struct rproc *rproc)
36 Note: to use this function you should already have a valid rproc
41 void rproc_shutdown(struct rproc *rproc)
43 In case @rproc is still being used by an additional user(s), then
49 - we're not decrementing the rproc's refcount, only the power refcount.
50 which means that the @rproc handle stays valid even after
58 /* in case we were given a valid 'rproc' handle */
59 int dummy_rproc_example(struct rproc *my_rproc)
81 struct rproc *rproc_alloc(struct device *dev, const char *name,
87 the name of the firmware to boot this rproc with, and the
88 length of private data needed by the allocating rproc driver (in bytes).
90 This function should be used by rproc implementations during
92 After creating an rproc handle using this function, and when ready,
95 On success, the new rproc is returned, and on failure, NULL.
97 Note: _never_ directly deallocate @rproc, even if it was not registered
100 void rproc_put(struct rproc *rproc)
101 - Free an rproc handle that was allocated by rproc_alloc.
103 rproc's refcount. It doesn't directly free rproc; that would happen
104 only if there are no other references to rproc and its refcount now
107 int rproc_add(struct rproc *rproc)
108 - Register @rproc with the remoteproc framework, after it has been
110 This is called by the platform-specific rproc implementation, whenever
114 context, which will look for virtio devices supported by the rproc's
120 int rproc_del(struct rproc *rproc)
122 This function should be called when the platform specific rproc
123 implementation decides to remove the rproc device. it should
127 After rproc_del() returns, @rproc is still valid, and its
130 Returns 0 on success and -EINVAL if @rproc isn't valid.
132 void rproc_report_crash(struct rproc *rproc, enum rproc_crash_type type)
135 platform specific rproc implementation. This should not be called from a
151 int (*start)(struct rproc *rproc);
152 int (*stop)(struct rproc *rproc);
153 void (*kick)(struct rproc *rproc, int vqid);
160 The ->start() handler takes an rproc handle and should then power on the
161 device and boot it (use rproc->priv to access platform-specific private data).
162 The boot address, in case needed, can be found in rproc->bootaddr (remoteproc
166 The ->stop() handler takes an rproc handle and powers the device down.
169 The ->kick() handler takes an rproc handle, and an index of a virtqueue
281 type, and hand those resources to the platform-specific rproc driver to handle.