On Wed, Jan 16, 2013 at 7:53 PM, Will Deacon [off-list ref] wrote:

On Wed, Dec 26, 2012 at 01:53:15AM +0000, Cho KyongHo wrote:

quoted

notice: v6 patch-set is rebased on next/iommu-exynos branch of
linux-samsung.git.  This patch-set does not include 2 patches (05 and 06
patches in v5 patch-se) because they alread exist already in the branch.

Given that devicetree-discuss has been notably absent from discussion
surrounding the proposed binding, I think that including that patch in
linux-samsung.git and dropping it from this series is rather premature.

I have comments on the binding, so I'll dig up the version you posted in v5
and add devicetree-discuss to CC.

Thank you.

quoted

The current exynos-iommu(System MMU) driver does not work autonomously
since it is lack of support for power management of peripheral blocks.
For example, MFC device driver must ensure that its System MMU is disabled
before MFC block is power-down not to invalidate IOTLB in the System MMU
when I/O memory mapping is changed. Because A System MMU is resides in the
same H/W block, access to control registers of System MMU while the H/W
block is turned off must be prohibited.

This set of changes solves the above problem with setting each System MMUs
as the parent of the device which owns the System MMU to recieve the
information when the device is turned off or turned on.

Another big change to the driver is the support for devicetree.
The bindings for System MMU is described in
Documentation/devicetree/bindings/arm/samsung/system-mmu.txt

This should probably be Documentation/devicetree/bindings/iommu/ no?

Please let me check it.

Thank you.

KyongHo.