Skip to content

Commit

Permalink
remoteproc: do not require an iommu
Browse files Browse the repository at this point in the history
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.

[[email protected]: write commit log]

Signed-off-by: Mark Grosen <[email protected]>
Signed-off-by: Ohad Ben-Cohen <[email protected]>
  • Loading branch information
Mark Grosen authored and ohadbc committed Feb 8, 2012
1 parent 779b96d commit 0798e1d
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions drivers/remoteproc/remoteproc_core.c
Original file line number Diff line number Diff line change
Expand Up @@ -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);
Expand Down

0 comments on commit 0798e1d

Please sign in to comment.