[PATCH v7 0/2] iommu/exynos: Add IOMMU/System MMU driver for Samsung Exynos
kmpark at infradead.org
Tue Dec 6 07:47:21 EST 2011
On Tue, Dec 6, 2011 at 9:13 PM, KyongHo Cho <pullip.cho at samsung.com> wrote:
> On Tue, Dec 6, 2011 at 8:24 AM, Kyungmin Park <kmpark at infradead.org> wrote:
>> On 12/6/11, Joerg Roedel <joerg.roedel at amd.com> wrote:
>>> On Fri, Nov 18, 2011 at 06:47:28PM +0900, KyongHo Cho wrote:
>>>> Patch Summary:
>>>> [PATCH v7 1/2] ARM: EXYNOS: Change System MMU platform device definitions
>>>> [PATCH v7 2/2] iommu/exynos: Add iommu driver for Exynos Platforms
>>> Okay, I merged it into arm/exynos, but it is not pushed yet. Actually
>>> there were conflicts while merging, which I resolved. What I failed
>>> to find is a config for Exynos that actually builds for upstream Linux.
>>> Probably I havn't tried hard enough to find one... Can you provide a
>>> kernel config that I can use for my testing and that builds a current
>>> 3.2-rc4 kernel for Exynos?
>> and I hope to see the real example how to use it with exynos platform.
>> Now I can't find the interface between exynos platform and generic exynos iommu.
> In "[PATCH v7 1/2] ARM: EXYNOS: Change System MMU platform device
> definitions" patch,
> you can find sysmmu_init().
> It stores associations between a system MMU and a peripheral device in
> platform data of platform device descriptor.
> If Exynos IOMMU driver finds the association while probing, then the
> driver can control the system MMU.
Maybe it's still call the function directly instead of using struct
dev field as OMAP did.
Even though generic DMA mapping IOMMU doesn't used, you can connect
the iommu field at arch/arm/include/asm/device.h
>> BTW, how do you test it at mainline kernel?
> I merged IOMMU mainline branch to our kernel branch and tested it with
> our FIMC, MFC, JPEG, 2D.
More information about the linux-arm-kernel