iommu/exynos: Fix arm64 allmodconfig build
Subsystems (2)
PATCH 1/1 iommu/exynos: Fix arm64 allmodconfig build
The Exynos IOMMU driver uses the ARM specific dmac_flush_range() and outer_flush_range() functions. This breaks the build on arm64 allmodconfig in -next since support has been merged for some Exynos ARMv8 SoCs. Add a dependency on ARM to keep things building until either the driver has the ARM dependencies removed or the ARMv8 architecture code implements these ARM specific APIs.
--- drivers/iommu/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/iommu/Kconfig +1 -1
@@ -187,7 +187,7 @@ config TEGRA_IOMMU_SMMU config EXYNOS_IOMMU bool "Exynos IOMMU Support" - depends on ARCH_EXYNOS + depends on ARCH_EXYNOS && ARM select IOMMU_API select ARM_DMA_USE_IOMMU help
Signature · 1 line
2.1.3
PATCH 1/1 iommu/exynos: Fix arm64 allmodconfig build
Quoted 6 lines · Mark Brown
The Exynos IOMMU driver uses the ARM specific
dmac_flush_range()andouter_flush_range()functions. This breaks the build on arm64 allmodconfig in -next since support has been merged for some Exynos ARMv8 SoCs. Add a dependency on ARM to keep things building until either the driver has the ARM dependencies removed or the ARMv8 architecture code implements these ARM specific APIs.
Hi Mark,
Few days ago I posted similar patch:
https://lkml.org/lkml/2014/12/5/268
but no one have picked it up.
Anyway the fix of yours seems fine to me.
Best regards,
Krzysztof
Quoted 20 lines
Signed-off-by Mark Brown <[email protected]>--- drivers/iommu/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)drivers/iommu/Kconfig +1
-1@@ -187,7 +187,7 @@ config TEGRA_IOMMU_SMMU config EXYNOS_IOMMU bool "Exynos IOMMU Support" - depends on ARCH_EXYNOS + depends on ARCH_EXYNOS && ARM select IOMMU_API select ARM_DMA_USE_IOMMU help
PATCH 1/1 iommu/exynos: Fix arm64 allmodconfig build
Quoted 7 lines · Krzysztof Koz?owski
Hi Mark,
Few days ago I posted similar patch:
https://lkml.org/lkml/2014/12/5/268
but no one have picked it up.Anyway the fix of yours seems fine to me.
I don't mind either way, it just seemed to be easier to report the bug
with a patch. If Jeorg is busy perhaps it can go via the arm64 tree,
the issue is triggered by the addition of the platform there?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141215/9a3567c7/attachment.sig>
PATCH 1/1 iommu/exynos: Fix arm64 allmodconfig build
Quoted 10 lines · Mark Brown
Quoted 5 lines · Krzysztof Koz?owski
Few days ago I posted similar patch:
https://lkml.org/lkml/2014/12/5/268
but no one have picked it up.Anyway the fix of yours seems fine to me.
I don't mind either way, it just seemed to be easier to report the bug with a patch. If Jeorg is busy perhaps it can go via the arm64 tree, the issue is triggered by the addition of the platform there?
Can I pass the buck to arm-soc, as they're handling arm64 platform code?
It seems sensible to merge the fix via the same tree that introduced the breakage.
Will
PATCH 1/1 iommu/exynos: Fix arm64 allmodconfig build
Quoted 10 lines · Will Deacon
Quoted 3 lines · Mark Brown
I don't mind either way, it just seemed to be easier to report the bug with a patch. If Jeorg is busy perhaps it can go via the arm64 tree, the issue is triggered by the addition of the platform there?
Can I pass the buck to arm-soc, as they're handling arm64 platform code?
It seems sensible to merge the fix via the same tree that introduced the breakage.
Sure, just resending to them...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141215/e01a2f66/attachment.sig>