* linux-next: manual merge of the tip tree with the amlogic tree
@ 2025-11-20 4:04 Stephen Rothwell
2025-11-20 7:46 ` Neil Armstrong
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2025-11-20 4:04 UTC (permalink / raw)
To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra,
Kevin Hilman, Neil Armstrong
Cc: Linux Kernel Mailing List, Linux Next Mailing List, Xianwei Zhao
[-- Attachment #1: Type: text/plain, Size: 1571 bytes --]
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
arch/arm64/boot/dts/amlogic/amlogic-s6.dtsi
between commit:
fe85b8876768 ("arm64: dts: amlogic: s6: add ao secure node")
from the amlogic tree and commit:
4b6111d677c7 ("arm64: dts: amlogic: Add gpio_intc node for Amlogic S6 SoCs")
from the tip 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 arch/arm64/boot/dts/amlogic/amlogic-s6.dtsi
index da3e607aea85,f91368bc2c48..000000000000
--- a/arch/arm64/boot/dts/amlogic/amlogic-s6.dtsi
+++ b/arch/arm64/boot/dts/amlogic/amlogic-s6.dtsi
@@@ -200,13 -190,15 +200,23 @@@
};
};
+ gpio_intc: interrupt-controller@4080 {
+ compatible = "amlogic,s6-gpio-intc",
+ "amlogic,meson-gpio-intc";
+ reg = <0x0 0x4080 0x0 0x20>;
+ interrupt-controller;
+ #interrupt-cells = <2>;
+ amlogic,channel-interrupts =
+ <10 11 12 13 14 15 16 17 18 19 20 21>;
+ };
++
+ ao-secure@10220 {
+ compatible = "amlogic,s6-ao-secure",
+ "amlogic,meson-gx-ao-secure",
+ "syscon";
+ reg = <0x0 0x10220 0x0 0x140>;
+ amlogic,has-chip-id;
+ };
};
};
};
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* linux-next: manual merge of the tip tree with the amlogic tree
@ 2025-11-20 4:08 Stephen Rothwell
0 siblings, 0 replies; 3+ messages in thread
From: Stephen Rothwell @ 2025-11-20 4:08 UTC (permalink / raw)
To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra,
Kevin Hilman, Neil Armstrong
Cc: Linux Kernel Mailing List, Linux Next Mailing List, Xianwei Zhao
[-- Attachment #1: Type: text/plain, Size: 1579 bytes --]
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
arch/arm64/boot/dts/amlogic/amlogic-s7d.dtsi
between commit:
e490b52477b8 ("arm64: dts: amlogic: s7d: add ao secure node")
from the amlogic tree and commit:
1d787348123b ("arm64: dts: amlogic: Add gpio_intc node for Amlogic S7D SoCs")
from the tip 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 arch/arm64/boot/dts/amlogic/amlogic-s7d.dtsi
index e60167af0390,5ef16820b574..000000000000
--- a/arch/arm64/boot/dts/amlogic/amlogic-s7d.dtsi
+++ b/arch/arm64/boot/dts/amlogic/amlogic-s7d.dtsi
@@@ -195,13 -185,15 +195,23 @@@
};
};
+ gpio_intc: interrupt-controller@4080 {
+ compatible = "amlogic,s7d-gpio-intc",
+ "amlogic,meson-gpio-intc";
+ reg = <0x0 0x4080 0x0 0x20>;
+ interrupt-controller;
+ #interrupt-cells = <2>;
+ amlogic,channel-interrupts =
+ <10 11 12 13 14 15 16 17 18 19 20 21>;
+ };
++
+ ao-secure@10220 {
+ compatible = "amlogic,s7d-ao-secure",
+ "amlogic,meson-gx-ao-secure",
+ "syscon";
+ reg = <0x0 0x10220 0x0 0x140>;
+ amlogic,has-chip-id;
+ };
};
};
};
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: linux-next: manual merge of the tip tree with the amlogic tree
2025-11-20 4:04 linux-next: manual merge of the tip tree with the amlogic tree Stephen Rothwell
@ 2025-11-20 7:46 ` Neil Armstrong
0 siblings, 0 replies; 3+ messages in thread
From: Neil Armstrong @ 2025-11-20 7:46 UTC (permalink / raw)
To: Stephen Rothwell, Thomas Gleixner, Ingo Molnar, H. Peter Anvin,
Peter Zijlstra, Kevin Hilman
Cc: Linux Kernel Mailing List, Linux Next Mailing List, Xianwei Zhao
Hi,
On 11/20/25 05:04, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the tip tree got a conflict in:
>
> arch/arm64/boot/dts/amlogic/amlogic-s6.dtsi
>
> between commit:
>
> fe85b8876768 ("arm64: dts: amlogic: s6: add ao secure node")
>
> from the amlogic tree and commit:
>
> 4b6111d677c7 ("arm64: dts: amlogic: Add gpio_intc node for Amlogic S6 SoCs")
Thanks, I wasn't aware those DT patches were merged via another tree.
I'll remove my patches for now.
Neil
>
> from the tip 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.
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-11-20 7:46 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-11-20 4:04 linux-next: manual merge of the tip tree with the amlogic tree Stephen Rothwell
2025-11-20 7:46 ` Neil Armstrong
-- strict thread matches above, loose matches on Subject: below --
2025-11-20 4:08 Stephen Rothwell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox