Lines Matching full:remoteproc

17 The remoteproc framework allows different platforms/architectures to
22 platform-specific remoteproc drivers only need to provide a few low-level
28 remoteproc will add those devices. This makes it possible to reuse the
84   #include <linux/remoteproc.h>
151 Register @rproc with the remoteproc framework, after it has been
186 Report a crash in a remoteproc
190 non-remoteproc driver. This function can be called from atomic/interrupt
196 These callbacks should be provided by platform-specific remoteproc
211 Every remoteproc implementation should at least provide the ->start and ->stop
217 The boot address, in case needed, can be found in rproc->bootaddr (remoteproc
234 At this point remoteproc supports ELF32 and ELF64 firmware binaries. However,
299 of specific remoteproc configuration. Other entries require the host to
337 dedicated structure in include/linux/remoteproc.h.
343 Virtio and remoteproc
346 The firmware should provide remoteproc information about virtio devices
351 When a new remote processor is registered, the remoteproc framework