Linux-Next discussions
 help / color / mirror / Atom feed
* linux-next: manual merge of the iommu tree with the arm-soc tree
@ 2016-02-29  4:16 Stephen Rothwell
  0 siblings, 0 replies; 5+ messages in thread
From: Stephen Rothwell @ 2016-02-29  4:16 UTC (permalink / raw)
  To: Joerg Roedel, Olof Johansson, Arnd Bergmann, linux-arm-kernel
  Cc: linux-next, linux-kernel, Yong Wu, Andrew-CT Chen,
	Matthias Brugger

Hi Joerg,

Today's linux-next merge of the iommu tree got a conflict in:

  arch/arm64/boot/dts/mediatek/mt8173.dtsi

between commit:

  93e9f5ee1e35 ("dts: arm64: Add EFUSE device node")

from the arm-soc tree and commit:

  5ff6b3a6d391 ("dts: mt8173: Add iommu/smi nodes for mt8173")

from the iommu tree.

I fixed it up (see below) and can carry the fix as necessary (no action
is required).

-- 
Cheers,
Stephen Rothwell

diff --cc arch/arm64/boot/dts/mediatek/mt8173.dtsi
index f4bd3c9182ad,804881181fcc..000000000000
--- a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
+++ b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
@@@ -277,11 -278,17 +278,22 @@@
  			reg = <0 0x10200620 0 0x20>;
  		};
  
+ 		iommu: iommu@10205000 {
+ 			compatible = "mediatek,mt8173-m4u";
+ 			reg = <0 0x10205000 0 0x1000>;
+ 			interrupts = <GIC_SPI 139 IRQ_TYPE_LEVEL_LOW>;
+ 			clocks = <&infracfg CLK_INFRA_M4U>;
+ 			clock-names = "bclk";
+ 			mediatek,larbs = <&larb0 &larb1 &larb2
+ 					  &larb3 &larb4 &larb5>;
+ 			#iommu-cells = <1>;
+ 		};
+ 
 +		efuse: efuse@10206000 {
 +			compatible = "mediatek,mt8173-efuse";
 +			reg = <0 0x10206000 0 0x1000>;
 +		};
 +
  		apmixedsys: clock-controller@10209000 {
  			compatible = "mediatek,mt8173-apmixedsys";
  			reg = <0 0x10209000 0 0x1000>;

^ permalink raw reply	[flat|nested] 5+ messages in thread

* linux-next: manual merge of the iommu tree with the arm-soc tree
@ 2022-05-06  2:39 Stephen Rothwell
  0 siblings, 0 replies; 5+ messages in thread
From: Stephen Rothwell @ 2022-05-06  2:39 UTC (permalink / raw)
  To: Joerg Roedel, Olof Johansson, Arnd Bergmann
  Cc: ARM, Joerg Roedel, Linux Kernel Mailing List,
	Linux Next Mailing List, Sven Peter

[-- Attachment #1: Type: text/plain, Size: 1968 bytes --]

Hi all,

Today's linux-next merge of the iommu tree got a conflict in:

  MAINTAINERS

between commit:

  a12d521f4a3d ("dt-bindings: iommu: Add Apple SART DMA address filter")

from the arm-soc tree and commit:

  ee5354345242 ("MAINTAINERS: Merge DART into ARM/APPLE MACHINE")

from the iommu tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc MAINTAINERS
index 83a61d719d95,7d728a19e857..000000000000
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@@ -1837,9 -1829,8 +1829,10 @@@ F:	Documentation/devicetree/bindings/ar
  F:	Documentation/devicetree/bindings/clock/apple,nco.yaml
  F:	Documentation/devicetree/bindings/i2c/apple,i2c.yaml
  F:	Documentation/devicetree/bindings/interrupt-controller/apple,*
 +F:	Documentation/devicetree/bindings/iommu/apple,sart.yaml
+ F:	Documentation/devicetree/bindings/iommu/apple,dart.yaml
  F:	Documentation/devicetree/bindings/mailbox/apple,mailbox.yaml
 +F:	Documentation/devicetree/bindings/nvme/apple,nvme-ans.yaml
  F:	Documentation/devicetree/bindings/pci/apple,pcie.yaml
  F:	Documentation/devicetree/bindings/pinctrl/apple,pinctrl.yaml
  F:	Documentation/devicetree/bindings/power/apple*
@@@ -1848,9 -1839,9 +1841,10 @@@ F:	arch/arm64/boot/dts/apple
  F:	drivers/clk/clk-apple-nco.c
  F:	drivers/i2c/busses/i2c-pasemi-core.c
  F:	drivers/i2c/busses/i2c-pasemi-platform.c
+ F:	drivers/iommu/apple-dart.c
  F:	drivers/irqchip/irq-apple-aic.c
  F:	drivers/mailbox/apple-mailbox.c
 +F:	drivers/nvme/host/apple.c
  F:	drivers/pinctrl/pinctrl-apple-gpio.c
  F:	drivers/soc/apple/*
  F:	drivers/watchdog/apple_wdt.c

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* linux-next: manual merge of the iommu tree with the arm-soc tree
@ 2026-05-18 13:06 Mark Brown
  2026-05-18 15:17 ` Krzysztof Kozlowski
  0 siblings, 1 reply; 5+ messages in thread
From: Mark Brown @ 2026-05-18 13:06 UTC (permalink / raw)
  To: Joerg Roedel
  Cc: Arnd Bergmann, Benjamin Gaignard, Joerg Roedel,
	Krzysztof Kozlowski, Linux Kernel Mailing List,
	Linux Next Mailing List

[-- Attachment #1: Type: text/plain, Size: 1634 bytes --]

Hi all,

Today's linux-next merge of the iommu tree got a conflict in:

  arch/arm64/configs/defconfig

between commit:

  f54f7979ff88d ("arm64: defconfig: Move entries to match savedefconfig")

from the arm-soc tree and commit:

  187029b922d0e ("arm64: defconfig: enable Verisilicon IOMMU for Rockchip RK3588")

from the iommu tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

diff --cc arch/arm64/configs/defconfig
index 9f00e2823ccb6,2755960fce06a..0000000000000
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@@ -1587,22 -1608,23 +1587,23 @@@ CONFIG_RENESAS_OSTM=
  CONFIG_ARM_MHU=y
  CONFIG_EXYNOS_MBOX=m
  CONFIG_IMX_MBOX=y
 -CONFIG_OMAP2PLUS_MBOX=m
  CONFIG_PLATFORM_MHU=y
 +CONFIG_OMAP2PLUS_MBOX=m
  CONFIG_BCM2835_MBOX=y
  CONFIG_QCOM_APCS_IPC=y
 +CONFIG_TEGRA_HSP_MBOX=y
  CONFIG_MTK_ADSP_MBOX=m
  CONFIG_QCOM_CPUCP_MBOX=m
 -CONFIG_TEGRA_HSP_MBOX=y
  CONFIG_QCOM_IPCC=y
  CONFIG_CIX_MBOX=y
 -CONFIG_ROCKCHIP_IOMMU=y
 -CONFIG_TEGRA_IOMMU_SMMU=y
  CONFIG_ARM_SMMU=y
  CONFIG_ARM_SMMU_V3=y
 -CONFIG_MTK_IOMMU=y
  CONFIG_QCOM_IOMMU=y
 +CONFIG_ROCKCHIP_IOMMU=y
 +CONFIG_TEGRA_IOMMU_SMMU=y
  CONFIG_APPLE_DART=m
 +CONFIG_MTK_IOMMU=y
+ CONFIG_VSI_IOMMU=m
  CONFIG_REMOTEPROC=y
  CONFIG_IMX_REMOTEPROC=y
  CONFIG_MTK_SCP=m

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: linux-next: manual merge of the iommu tree with the arm-soc tree
  2026-05-18 13:06 linux-next: manual merge of the iommu tree with the arm-soc tree Mark Brown
@ 2026-05-18 15:17 ` Krzysztof Kozlowski
  2026-05-19  8:56   ` Joerg Roedel
  0 siblings, 1 reply; 5+ messages in thread
From: Krzysztof Kozlowski @ 2026-05-18 15:17 UTC (permalink / raw)
  To: Mark Brown, Joerg Roedel
  Cc: Arnd Bergmann, Benjamin Gaignard, Joerg Roedel,
	Linux Kernel Mailing List, Linux Next Mailing List

On 18/05/2026 15:06, Mark Brown wrote:
> Hi all,
> 
> Today's linux-next merge of the iommu tree got a conflict in:
> 
>   arch/arm64/configs/defconfig
> 
> between commit:
> 
>   f54f7979ff88d ("arm64: defconfig: Move entries to match savedefconfig")
> 
> from the arm-soc tree and commit:
> 
>   187029b922d0e ("arm64: defconfig: enable Verisilicon IOMMU for Rockchip RK3588")

This patch should rather not be taken by iommu tree.

Just like DTS this is patch for SoC platform. Joerg, could you drop it?
It's better if SoC platform maintainer handles the conflicts.

Best regards,
Krzysztof

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: linux-next: manual merge of the iommu tree with the arm-soc tree
  2026-05-18 15:17 ` Krzysztof Kozlowski
@ 2026-05-19  8:56   ` Joerg Roedel
  0 siblings, 0 replies; 5+ messages in thread
From: Joerg Roedel @ 2026-05-19  8:56 UTC (permalink / raw)
  To: Krzysztof Kozlowski
  Cc: Mark Brown, Arnd Bergmann, Benjamin Gaignard, Joerg Roedel,
	Linux Kernel Mailing List, Linux Next Mailing List

On Mon, May 18, 2026 at 05:17:07PM +0200, Krzysztof Kozlowski wrote:
> >   187029b922d0e ("arm64: defconfig: enable Verisilicon IOMMU for Rockchip RK3588")
> 
> This patch should rather not be taken by iommu tree.
> 
> Just like DTS this is patch for SoC platform. Joerg, could you drop it?
> It's better if SoC platform maintainer handles the conflicts.

It is now dropped, will push out a new tree later today.

-Joerg

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2026-05-19  8:56 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-05-18 13:06 linux-next: manual merge of the iommu tree with the arm-soc tree Mark Brown
2026-05-18 15:17 ` Krzysztof Kozlowski
2026-05-19  8:56   ` Joerg Roedel
  -- strict thread matches above, loose matches on Subject: below --
2022-05-06  2:39 Stephen Rothwell
2016-02-29  4:16 Stephen Rothwell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox