remoteproc: do not require an iommu
authorMark Grosen <mgrosen@ti.com>
Tue, 13 Dec 2011 06:41:47 +0000 (08:41 +0200)
committerOhad Ben-Cohen <ohad@wizery.com>
Wed, 8 Feb 2012 20:54:11 +0000 (22:54 +0200)
commit0798e1da7a1cc467f56bfa5149a0eede5ae38f72
tree22fd7fdebb49fd5016687fc838d4f37233087ee6
parent779b96d20ca97cfa19162b340bff0c27b405b4b2
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 <mgrosen@ti.com>
Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
drivers/remoteproc/remoteproc_core.c
This page took 0.029897 seconds and 5 git commands to generate.