[PATCH 00/29] Exynos SYSMMU (IOMMU) integration with DT and DMA-mapping subsystem
m.szyprowski at samsung.com
Tue Aug 19 05:01:32 PDT 2014
On 2014-08-19 13:39, Andreas Färber wrote:
> Hi Marek and Inki,
> Am 19.08.2014 08:07, schrieb Marek Szyprowski:
>> On 2014-08-19 01:32, Joerg Roedel wrote:
>>> On Tue, Aug 05, 2014 at 12:47:28PM +0200, Marek Szyprowski wrote:
>>>> 33 files changed, 1016 insertions(+), 356 deletions(-)
>>> This touches a lot of non-iommu stuff. What is your strategy on getting
>>> this in, do you plan to get the non-iommu changes merged first or do you
>>> want to collect the respective Acks and merge this all through one tree?
>> Those patches are posted as one patchset mainly to demonstrate how to get
>> everything to work together. I also posted this as a single patch series
>> to get some feedback from other iommu developers, especially all those
>> involved in the generic iommu dt bindings.
>> For merging, I will split them into smaller series and try to get
>> respective acks.
> I'm working on 5250 based Spring Chromebook and noticed that v3.17-rc1
> got some more iommu support. With the new CONFIG_DRM_EXYNOS_IOMMU=y my
> machine stops booting. So I'm wondering, is any of this a fix for 3.17,
> or is all of this "unrelated" -next material?
This is probably a side effect of patch
("iommu/exynos: Select ARM_DMA_USE_IOMMU"). It added selection of
symbol, on which IOMMU support in Exynos DRM subsystem depends. However
this symbol is all that this patch does, without providing any code code
implements real support for ARM DMA IOMMU integration, which is needed
DRM driver. Please disable CONFIG_DRM_EXYNOS_IOMMU in kernel .config and
system should be bootable again.
> Also, are you or someone
> working on the respective DT changes for Exynos5?
I can prepare DT changes for Exynos5 as well, but first I wanted to
everyone involved in generic IOMMU bindings and Exynos IOMMU driver
agrees on my
Marek Szyprowski, PhD
Samsung R&D Institute Poland
More information about the linux-arm-kernel