Le 22/10/2026 à 20:29, Tom Rini a écrit :
On Thu, Oct 22, 2026 at 10:08:23AM +0200, Richard Genoud (Synaptics) wrote:

Introduce mach-synaptics to support SL2619 SoC-based boards. This adds
the platform Kconfig and build infrastructure, along with initial
SL2619 RDK board support and defconfig

Introduce SYNAPTICS_SL2619, which selects ARM64, along with ARCH_SYNAPTICS
which selects driver model, SYS_NS16550 and GIC-v2.

Signed-off-by: Richard Genoud (Synaptics) <[email protected]>
[snip]
+ARM SYNAPTICS
+M:     Richard Genoud <[email protected]>
+M:     Terry Zhou <[email protected]>
+S:     Maintained
+F:     arch/arm/dts/sl2619-rdk-u-boot.dtsi
+F:     arch/arm/mach-synaptics/
+F:     board/synaptics/
+F:     configs/synaptics_*
+F:     doc/board/synaptics/
+F:     include/configs/synaptics_*.h

Use "N: synaptics" instead to cover most of these.

Ok.

+
  ARM TEGRA
  M:    Thierry Reding <[email protected]>
  M:    Svyatoslav Ryhel <[email protected]>
[snip]
diff --git a/arch/arm/dts/sl2619-rdk-u-boot.dtsi 
b/arch/arm/dts/sl2619-rdk-u-boot.dtsi
new file mode 100644
index 000000000000..a886ed7355ff
--- /dev/null
+++ b/arch/arm/dts/sl2619-rdk-u-boot.dtsi
@@ -0,0 +1,5 @@
+// SPDX-License-Identifier: GPL-2.0+
+
+&sm_uart0 {
+       clock-frequency = <25000000>;
+};

Isn't this allowed upstream?
Definitely.
Jisheng, maybe you could add it in the DTS in your v2?


diff --git a/arch/arm/mach-synaptics/Kconfig b/arch/arm/mach-synaptics/Kconfig
new file mode 100644
index 000000000000..33282060a8e0
--- /dev/null
+++ b/arch/arm/mach-synaptics/Kconfig
@@ -0,0 +1,36 @@
+if ARCH_SYNAPTICS
+
+config SYS_SOC
+       default "synaptics"
+
+config SYS_VENDOR
+       default "synaptics"
+
+config SYNAPTICS_SL2619
+       bool "Synaptics SL2619 SoC"
+       select ARM64

Shouldn't this be with the ARCH symbol? Or are there 32bit cores you'll
be supporting later?

Indeed, I think it's safe to say that there will be only 64bits.
I'll change that

Otherwise seems quite reasonable and I'm glad to see this posted,
thanks!

Great!
Thanks!

Regards,
Richard

Reply via email to