linux-kernel - Re: [PATCH 00/29] Exynos SYSMMU (IOMMU) integration with DT and DMA-mapping subsystem

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]

Message-ID: <20140818233201.GL9809@8bytes.org>
Date:	Tue, 19 Aug 2014 01:32:01 +0200
From:	Joerg Roedel <joro@...tes.org>
To:	Marek Szyprowski <m.szyprowski@...sung.com>
Cc:	iommu@...ts.linux-foundation.org,
	linux-samsung-soc@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	linaro-mm-sig@...ts.linaro.org, Arnd Bergmann <arnd@...db.de>,
	Shaik Ameer Basha <shaik.ameer@...sung.com>,
	Cho KyongHo <pullip.cho@...sung.com>,
	Thierry Reding <treding@...dia.com>,
	Olof Johansson <olof@...om.net>,
	Laurent Pinchart <laurent.pinchart@...asonboard.com>,
	Rob Herring <robh@...nel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Inki Dae <inki.dae@...sung.com>,
	Kukjin Kim <kgene.kim@...sung.com>,
	Sylwester Nawrocki <s.nawrocki@...sung.com>,
	Tomasz Figa <tomasz.figa@...il.com>,
	Kyungmin Park <kyungmin.park@...sung.com>
Subject: Re: [PATCH 00/29] Exynos SYSMMU (IOMMU) integration with DT and
 DMA-mapping subsystem

On Tue, Aug 05, 2014 at 12:47:28PM +0200, Marek Szyprowski wrote:
>  .../devicetree/bindings/iommu/samsung,sysmmu.txt   |  93 ++-
>  Documentation/power/notifiers.txt                  |  14 +
>  arch/arm/boot/dts/exynos4.dtsi                     | 118 ++++
>  arch/arm/boot/dts/exynos4210.dtsi                  |  23 +
>  arch/arm/boot/dts/exynos4x12.dtsi                  |  82 +++
>  arch/arm/include/asm/dma-iommu.h                   |  36 ++
>  arch/arm/mach-exynos/pm_domains.c                  |  12 +-
>  arch/arm/mach-integrator/impd1.c                   |   2 +-
>  arch/arm/mm/dma-mapping.c                          |  47 ++
>  drivers/base/bus.c                                 |   4 +-
>  drivers/base/dd.c                                  |  10 +-
>  drivers/base/platform.c                            |   2 +-
>  drivers/base/power/domain.c                        |  70 ++-
>  drivers/clk/samsung/clk-exynos4.c                  |   1 +
>  drivers/gpu/drm/exynos/exynos_drm_fimc.c           |   1 +
>  drivers/gpu/drm/exynos/exynos_drm_fimd.c           |  26 +-
>  drivers/gpu/drm/exynos/exynos_drm_g2d.c            |   1 +
>  drivers/gpu/drm/exynos/exynos_drm_gsc.c            |   1 +
>  drivers/gpu/drm/exynos/exynos_drm_rotator.c        |   1 +
>  drivers/gpu/drm/exynos/exynos_mixer.c              |   1 +
>  drivers/iommu/exynos-iommu.c                       | 663 +++++++++++++--------
>  drivers/iommu/iommu.c                              |   3 +
>  drivers/media/platform/s5p-mfc/s5p_mfc.c           | 107 ++--
>  drivers/pci/host/pci-mvebu.c                       |   2 +-
>  drivers/pci/host/pci-rcar-gen2.c                   |   2 +-
>  drivers/pci/host/pci-tegra.c                       |   2 +-
>  drivers/pci/host/pcie-rcar.c                       |   2 +-
>  drivers/soc/tegra/pmc.c                            |   2 +-
>  include/dt-bindings/clock/exynos4.h                |  10 +-
>  include/linux/device.h                             |  12 +-
>  include/linux/iommu.h                              |   1 +
>  include/linux/pm.h                                 |   2 +
>  include/linux/pm_domain.h                          |  19 +
>  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?


	Joerg

--
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/