Lines Matching full:virtio

20 duplicated. In addition, this framework also adds rpmsg virtio devices
24 (for more information about the virtio-based rpmsg bus and its drivers,
26 Registration of other types of virtio devices is now also possible. Firmwares
27 just need to publish what kind of virtio devices do they support, and then
29 existing virtio drivers with remote processor backends at a minimal development
159 context, which will look for virtio devices supported by the rproc's
162 If found, those virtio devices will be created and added, so as a result
163 of registering this remote processor, additional virtio drivers might get
212 handlers. If rpmsg/virtio functionality is also desired, then the ->kick handler
258 supported virtio devices (and their configurations).
315    * @RSC_VDEV:       declare support for a virtio device, and serve as its
316    *		    virtio header.
343 Virtio and remoteproc
346 The firmware should provide remoteproc information about virtio devices
348 should specify the virtio device id (as in virtio_ids.h), virtio features,
349 virtio config space, vrings information, etc.
352 will look for its resource table and will register the virtio devices
353 it supports. A firmware may support any number of virtio devices, and
355 rpmsg virtio devices this way, if desired).
358 allocation of virtio devices. Dynamic allocations will also be made possible