On Wed, Apr 30, 2014 at 04:27:10PM +0530, Shaik Ameer Basha wrote:
This series is going on for quite a long time and most of the patches here
doesn't depend on dt bindings. As Exynos IOMMU h/w is introducing new versions
very frequently, maintaining and reviewing all these patches again and
On 06.05.2014 19:59, Joerg Roedel wrote:
On Wed, Apr 30, 2014 at 04:27:10PM +0530, Shaik Ameer Basha wrote:
This series is going on for quite a long time and most of the patches here
doesn't depend on dt bindings. As Exynos IOMMU h/w is introducing new versions
very frequently, maintaining and
On Tuesday 06 May 2014 19:59:05 Joerg Roedel wrote:
On Wed, Apr 30, 2014 at 04:27:10PM +0530, Shaik Ameer Basha wrote:
This series is going on for quite a long time and most of the patches here
doesn't depend on dt bindings. As Exynos IOMMU h/w is introducing new
versions
very
On Tue, 06 May 2014 20:08:47 +0200, Tomasz Figa wrote:
On 06.05.2014 19:59, Joerg Roedel wrote:
On Wed, Apr 30, 2014 at 04:27:10PM +0530, Shaik Ameer Basha wrote:
This series is going on for quite a long time and most of the patches here
doesn't depend on dt bindings. As Exynos IOMMU h/w is
On Mon, Apr 28, 2014 at 2:04 PM, Arnd Bergmann a...@arndb.de wrote:
On Sunday 27 April 2014 13:07:32 Shaik Ameer Basha wrote:
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
On Sunday 27 April 2014 13:07:32 Shaik Ameer Basha wrote:
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
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