path: root/drivers/remoteproc/remoteproc_core.c
diff options
authorMark Grosen <mgrosen@ti.com>2011-12-13 09:14:15 +0200
committerOhad Ben-Cohen <ohad@wizery.com>2012-02-08 22:54:17 +0200
commit7d2d3956fbc1aa9a3ccdc9389b88505232764d4f (patch)
tree6c217bb8b541801b9e51a66d7ee1f8f47f6789e2 /drivers/remoteproc/remoteproc_core.c
parent0798e1da7a1cc467f56bfa5149a0eede5ae38f72 (diff)
remoteproc: avoid registering a virtio device if not supported
Let remoteproc know when the firmware doesn't support any virtio functionality, so registering a virtio device can be avoided. This is needed for remote processors that doesn't require any virtio-based communications, but are still controlled via remoteproc. [ohad@wizery.com: write commit log] Signed-off-by: Mark Grosen <mgrosen@ti.com> Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
Diffstat (limited to 'drivers/remoteproc/remoteproc_core.c')
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/remoteproc/remoteproc_core.c b/drivers/remoteproc/remoteproc_core.c
index 0d9a9552c31..080c0569ef3 100644
--- a/drivers/remoteproc/remoteproc_core.c
+++ b/drivers/remoteproc/remoteproc_core.c
@@ -695,7 +695,7 @@ static int
rproc_handle_virtio_rsc(struct rproc *rproc, struct fw_resource *rsc, int len)
struct device *dev = rproc->dev;
- int ret = 0;
+ int ret = -ENODEV;
for (; len >= sizeof(*rsc); rsc++, len -= sizeof(*rsc))
if (rsc->type == RSC_VIRTIO_DEV) {