Skip to content

Exynos SYSMMU (IOMMU) dts and arch updates

Krzysztof Kozlowski linux-arm-kernel linux-iommu linux-samsung-soc 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 6 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 6 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/6] Exynos SYSMMU (IOMMU) dts and arch updates
Quoted 32 lines · Krzysztof Kozlowski
Quoted 31 lines · Kukjin Kim
Quoted 11 lines · Krzysztof Kozlowski

W dniu 01.06.2015 o 19:10, Marek Szyprowski pisze:

Quoted 10 lines

Hello,

Main changes for Exynos SYSMMU (IOMMU) driver has been finally scheduled for merging - see
https://git.kernel.org/cgit/linux/kernel/git/joro/iommu.git/commit/?h=next
In meantime there have been quite a lot of changes related to Exynos DTS files queued for merging and my patches don't apply anymore. To ease merge process I've decided to rebased all Exynos SYSMMU dts changes onto latest exynos next tree from: https://github.com/krzk/linux dt-for-next

Quoted 7 lines
Quoted 4 lines

While rebasing I've fixes a few spotted issues: some nodes still used old 'samsung,power-domain' properties (now replaced with 'power-domains') and added properties to jpeg codec merged recently.

Thanks for rebasing this stuff.

Same here ;-)

Quoted 10 lines

I picked whole patchset with Javier's tested-by. I'll send it to Kukjin later or directly to arm-soc (depending what will happen with last pull request).

Kukjin, you mentioned that you will do something with this patchset the previous weekend. Since then nothing happened so I am not sure what are your plans... Can you share them? Do you want to pick it by yourself, do you have any comments or maybe you need something from our side? (I checked the patches and they look fine)

Quoted 4 lines
Quoted 1 line

Done, thanks.

Thank you, I tested the for-next branch on some of my boards and everything looked fine.

Oh, something wrong happened on some of configs/boards:

Arndale Octa: multi_v7_defconfig
Last tests on samsung tree fail:
1.
http://kernelci.org/boot/exynos5420-arndale-octa_rootfs:nfs/job/samsung/kernel/v4.1-rc6-146-g1c07c562d9d5/defconfig/multi_v7_defconfig/lab/lab-tbaker/?_id=556fbaee59b5146b5cda4447
2.
http://kernelci.org/boot/exynos5420-arndale-octa_rootfs:nfs/job/samsung/kernel/v4.1-rc6-137-g1730fe10f4a8/defconfig/multi_v7_defconfig/lab/lab-tbaker/?_id=556e948659b5144e74da4445

Odroid XU3: multi_v7_defconfig
Last commit fails:
http://kernelci.org/boot/exynos5422-odroidxu3_rootfs:nfs/job/samsung/kernel/v4.1-rc6-146-g1c07c562d9d5/defconfig/multi_v7_defconfig/lab/lab-tbaker/?_id=556fbb2d59b5146b63da4449

I can test tonight on Odroid XU3 but I don't have access to Arndale Octa board. Maybe guys from SRPOL could test it?

Best regards,
Krzysztof