lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 6 Dec 2011 21:13:18 +0900
From:	KyongHo Cho <pullip.cho@...sung.com>
To:	Kyungmin Park <kmpark@...radead.org>
Cc:	Joerg Roedel <joerg.roedel@....com>,
	linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
	Younglak Kim <younglak1004.kim@...sung.com>,
	iommu@...ts.linux-foundation.org,
	Kukjin Kim <kgene.kim@...sung.com>,
	Sanghyun Lee <sanghyun75.lee@...sung.com>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v7 0/2] iommu/exynos: Add IOMMU/System MMU driver for
 Samsung Exynos

On Tue, Dec 6, 2011 at 8:24 AM, Kyungmin Park <kmpark@...radead.org> wrote:
> On 12/6/11, Joerg Roedel <joerg.roedel@....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.

> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ