[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160621091732.GB28248@8bytes.org>
Date: Tue, 21 Jun 2016 11:17:32 +0200
From: Joerg Roedel <joro@...tes.org>
To: Tomasz Figa <tfiga@...omium.org>
Cc: iommu@...ts.linux-foundation.org, dri-devel@...ts.freedesktop.org,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
David Airlie <airlied@...ux.ie>,
Heiko Stuebner <heiko@...ech.de>,
Mark Yao <mark.yao@...k-chips.com>,
Shunqian Zheng <zhengsq@...k-chips.com>,
Daniel Kurtz <djkurtz@...omium.org>,
Marek Szyprowski <m.szyprowski@...sung.com>
Subject: Re: [PATCH v4 0/8] iommu/rockchip: Fix bugs and enable on ARM64
On Tue, Jun 21, 2016 at 01:34:33PM +0900, Tomasz Figa wrote:
> This series intends mostly to enable support for ARM64 architecture
> in the rockchip-iommu driver. On the way to do so, some bugs are also
> fixed.
>
> The most important changes here are:
> - making the Rockchip IOMMU driver use DMA API for managing cache
> coherency of page tables,
> - making the Rockchip DRM driver not use DMA API on behalf of a virtual
> device (behind a virtual IOMMU) to allocate and map buffers, but
> instead proper DRM helpers and IOMMU API directly.
Are these two parts dependent on each other or can the IOMMU and the DRM
part merged independently?
Joerg
Powered by blists - more mailing lists