From 0798e1da7a1cc467f56bfa5149a0eede5ae38f72 Mon Sep 17 00:00:00 2001 From: Mark Grosen Date: Tue, 13 Dec 2011 08:41:47 +0200 Subject: remoteproc: do not require an iommu Not all remote processors employ an IOMMU, so do not error out on !iommu_present(). Note: we currently still use iommu_present() to tell whether we need to configure an IOMMU or not. That works for simple cases, but will easily fail with more complicated ones (e.g. where an IOMMU exists, but not all remote processors use it). When those use cases show up, we will solve them by introducing something like remoteproc hw capabilities. [ohad@wizery.com: write commit log] Signed-off-by: Mark Grosen Signed-off-by: Ohad Ben-Cohen --- drivers/remoteproc/remoteproc_core.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'drivers/remoteproc') diff --git a/drivers/remoteproc/remoteproc_core.c b/drivers/remoteproc/remoteproc_core.c index ad93d7d4ecb..0d9a9552c31 100644 --- a/drivers/remoteproc/remoteproc_core.c +++ b/drivers/remoteproc/remoteproc_core.c @@ -105,8 +105,8 @@ static int rproc_enable_iommu(struct rproc *rproc) * that will be set by the remoteproc driver. */ if (!iommu_present(dev->bus)) { - dev_err(dev, "iommu not found\n"); - return -ENODEV; + dev_dbg(dev, "iommu not found\n"); + return 0; } domain = iommu_domain_alloc(dev->bus); -- cgit v1.2.3-70-g09d2