From: Richard GENOUD <richard.genoud@bootlin.com>
To: Jisheng Zhang <jszhang@kernel.org>, Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney+clk@redhat.com>,
Jerome Brunet <jbrunet+clk@baylibre.com>,
Linus Walleij <linusw@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2 13/13] arm64: dts: synaptics: add SL2610 family RDK boards
Date: Thu, 19 Nov 2026 10:23:47 +0100 [thread overview]
Message-ID: <53f65c05-1c09-410d-8f49-9175f46a0609@bootlin.com> (raw)
In-Reply-To: <20261115102401.3520-14-jszhang@kernel.org>
Le 15/11/2026 à 11:23, Jisheng Zhang a écrit :
> Add device trees for the SL2611, SL2613, SL2615, SL2617 and SL2619
> reference development kits. Share their common console, memory, pin
> configuration and regulator descriptions and enable the populated
> peripherals.
>
> Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
> ---
> arch/arm64/boot/dts/synaptics/Makefile | 5 +
> arch/arm64/boot/dts/synaptics/sl2611-rdk.dts | 16 +++
> arch/arm64/boot/dts/synaptics/sl2613-rdk.dts | 16 +++
> arch/arm64/boot/dts/synaptics/sl2615-rdk.dts | 16 +++
> arch/arm64/boot/dts/synaptics/sl2617-rdk.dts | 16 +++
> arch/arm64/boot/dts/synaptics/sl2619-rdk.dts | 16 +++
> .../boot/dts/synaptics/sl261x-rdk-common.dtsi | 135 ++++++++++++++++++
> 7 files changed, 220 insertions(+)
> create mode 100644 arch/arm64/boot/dts/synaptics/sl2611-rdk.dts
> create mode 100644 arch/arm64/boot/dts/synaptics/sl2613-rdk.dts
> create mode 100644 arch/arm64/boot/dts/synaptics/sl2615-rdk.dts
> create mode 100644 arch/arm64/boot/dts/synaptics/sl2617-rdk.dts
> create mode 100644 arch/arm64/boot/dts/synaptics/sl2619-rdk.dts
> create mode 100644 arch/arm64/boot/dts/synaptics/sl261x-rdk-common.dtsi
>
> diff --git a/arch/arm64/boot/dts/synaptics/Makefile b/arch/arm64/boot/dts/synaptics/Makefile
> index de71ddda6835..810d0d08c2de 100644
> --- a/arch/arm64/boot/dts/synaptics/Makefile
> +++ b/arch/arm64/boot/dts/synaptics/Makefile
> @@ -2,3 +2,8 @@
> # Berlin SoC Family
> dtb-$(CONFIG_ARCH_BERLIN) += berlin4ct-dmp.dtb
> dtb-$(CONFIG_ARCH_BERLIN) += berlin4ct-stb.dtb
> +dtb-$(CONFIG_ARCH_BERLIN) += sl2611-rdk.dtb
> +dtb-$(CONFIG_ARCH_BERLIN) += sl2613-rdk.dtb
> +dtb-$(CONFIG_ARCH_BERLIN) += sl2615-rdk.dtb
> +dtb-$(CONFIG_ARCH_BERLIN) += sl2617-rdk.dtb
> +dtb-$(CONFIG_ARCH_BERLIN) += sl2619-rdk.dtb
> diff --git a/arch/arm64/boot/dts/synaptics/sl2611-rdk.dts b/arch/arm64/boot/dts/synaptics/sl2611-rdk.dts
> new file mode 100644
> index 000000000000..585872307834
> --- /dev/null
> +++ b/arch/arm64/boot/dts/synaptics/sl2611-rdk.dts
> @@ -0,0 +1,16 @@
> +// SPDX-License-Identifier: (GPL-2.0 OR MIT)
> +/*
> + * Copyright (C) 2025 Synaptics Incorporated
> + *
> + * Author: Jisheng Zhang <jszhang@kernel.org>
> + */
> +
> +/dts-v1/;
> +
> +#include "sl2611.dtsi"
> +#include "sl261x-rdk-common.dtsi"
> +
> +/ {
> + model = "Synaptics SL2611 RDK";
> + compatible = "syna,sl2611-rdk", "syna,sl2611";
> +};
> diff --git a/arch/arm64/boot/dts/synaptics/sl2613-rdk.dts b/arch/arm64/boot/dts/synaptics/sl2613-rdk.dts
> new file mode 100644
> index 000000000000..de75c9fab6a2
> --- /dev/null
> +++ b/arch/arm64/boot/dts/synaptics/sl2613-rdk.dts
> @@ -0,0 +1,16 @@
> +// SPDX-License-Identifier: (GPL-2.0 OR MIT)
> +/*
> + * Copyright (C) 2025 Synaptics Incorporated
> + *
> + * Author: Jisheng Zhang <jszhang@kernel.org>
> + */
> +
> +/dts-v1/;
> +
> +#include "sl2613.dtsi"
> +#include "sl261x-rdk-common.dtsi"
> +
> +/ {
> + model = "Synaptics SL2613 RDK";
> + compatible = "syna,sl2613-rdk", "syna,sl2613";
> +};
> diff --git a/arch/arm64/boot/dts/synaptics/sl2615-rdk.dts b/arch/arm64/boot/dts/synaptics/sl2615-rdk.dts
> new file mode 100644
> index 000000000000..ae03638a3a53
> --- /dev/null
> +++ b/arch/arm64/boot/dts/synaptics/sl2615-rdk.dts
> @@ -0,0 +1,16 @@
> +// SPDX-License-Identifier: (GPL-2.0 OR MIT)
> +/*
> + * Copyright (C) 2025 Synaptics Incorporated
> + *
> + * Author: Jisheng Zhang <jszhang@kernel.org>
> + */
> +
> +/dts-v1/;
> +
> +#include "sl2615.dtsi"
> +#include "sl261x-rdk-common.dtsi"
> +
> +/ {
> + model = "Synaptics SL2615 RDK";
> + compatible = "syna,sl2615-rdk", "syna,sl2615";
> +};
> diff --git a/arch/arm64/boot/dts/synaptics/sl2617-rdk.dts b/arch/arm64/boot/dts/synaptics/sl2617-rdk.dts
> new file mode 100644
> index 000000000000..ba4ea21ac505
> --- /dev/null
> +++ b/arch/arm64/boot/dts/synaptics/sl2617-rdk.dts
> @@ -0,0 +1,16 @@
> +// SPDX-License-Identifier: (GPL-2.0 OR MIT)
> +/*
> + * Copyright (C) 2025 Synaptics Incorporated
> + *
> + * Author: Jisheng Zhang <jszhang@kernel.org>
> + */
> +
> +/dts-v1/;
> +
> +#include "sl2617.dtsi"
> +#include "sl261x-rdk-common.dtsi"
> +
> +/ {
> + model = "Synaptics SL2617 RDK";
> + compatible = "syna,sl2617-rdk", "syna,sl2617";
> +};
> diff --git a/arch/arm64/boot/dts/synaptics/sl2619-rdk.dts b/arch/arm64/boot/dts/synaptics/sl2619-rdk.dts
> new file mode 100644
> index 000000000000..58901ac2a050
> --- /dev/null
> +++ b/arch/arm64/boot/dts/synaptics/sl2619-rdk.dts
> @@ -0,0 +1,16 @@
> +// SPDX-License-Identifier: (GPL-2.0 OR MIT)
> +/*
> + * Copyright (C) 2025 Synaptics Incorporated
> + *
> + * Author: Jisheng Zhang <jszhang@kernel.org>
> + */
> +
> +/dts-v1/;
> +
> +#include "sl2619.dtsi"
> +#include "sl261x-rdk-common.dtsi"
> +
> +/ {
> + model = "Synaptics SL2619 RDK";
> + compatible = "syna,sl2619-rdk", "syna,sl2619";
> +};
> diff --git a/arch/arm64/boot/dts/synaptics/sl261x-rdk-common.dtsi b/arch/arm64/boot/dts/synaptics/sl261x-rdk-common.dtsi
> new file mode 100644
> index 000000000000..78a9b28fdf99
> --- /dev/null
> +++ b/arch/arm64/boot/dts/synaptics/sl261x-rdk-common.dtsi
> @@ -0,0 +1,135 @@
> +// SPDX-License-Identifier: (GPL-2.0 OR MIT)
> +/*
> + * Copyright (C) 2025 Synaptics Incorporated
> + *
> + * Author: Jisheng Zhang <jszhang@kernel.org>
> + */
> +
> +#include <dt-bindings/gpio/gpio.h>
> +#include <dt-bindings/input/linux-event-codes.h>
> +
> +/ {
> + aliases {
> + serial0 = &sm_uart0;
> + serial1 = &sm_uart1;
> + serial2 = &sm_uart2;
> + serial3 = &sm_uart3;
> + serial4 = &soc_uart0;
> + serial5 = &soc_uart1;
> + serial6 = &soc_uart2;
> + serial7 = &soc_uart3;
> + i2c0 = &sm_i2c0;
> + i2c1 = &sm_i2c1;
> + i2c2 = &soc_i2c0;
> + i2c3 = &soc_i2c1;
> + spi1 = &sm_spi1;
> + spi2 = &soc_spi0;
> + spi3 = &soc_spi1;
> + spi4 = &soc_spi2;
> + spi5 = &soc_spi3;
> + };
> +
> + cpus {
> + cpu@0 {
> + cpu0-supply = <&vcore>;
> + };
> + };
> +
> + chosen {
> + stdout-path = "serial0:115200n8";
> + bootargs = "earlycon";
> + };
> +
> + memory@0 {
> + device_type = "memory";
> + reg = <0x0 0x00000000 0x0 0x80000000>;
> + };
Some memory is dedicated to the trust zone:
tz 0x00100000 - 0x00600000 (secure)
bootloader 0x00600000 - 0x00D00000
NonSecure-NonCacheable 0x00D00000 - 0x01500000
system 0x01500000 - 0x7FFFFF00
(from mr_config)
Should it be added here as reserved-memory, or it's intended to be set
at run time by the bootloader?
I was thinking of something like:
reserved_memory: reserved-memory {
#address-cells = <2>;
#size-cells = <2>;
ranges;
tz: tz@100000 {
reg = <0x0 0x00100000 0x0 0x00500000>;
no-map;
};
};
> +};
> +
> +&osc {
> + clock-frequency = <25000000>;
> +};
> +
> +&pinctrl {
> + soc_i2c0_pmux: soc_i2c0-pmux {
> + groups = "GPIO23", "GPIO24";
> + function = "tw2";
> + drive-strength = <7>;
> + };
> +};
> +
> +&sm_pinctrl {
> + sm_i2c0_pmux: i2c0-pmux {
> + groups = "SM_GPIO12", "SM_GPIO13";
> + function = "tw0";
> + drive-strength = <7>;
> + };
> +
> + sm_i2c1_pmux: i2c1-pmux {
> + groups = "SM_GPIO3", "SM_GPIO4";
> + function = "tw1";
> + drive-strength = <7>;
> + };
> +
> + vcore_gpio_pmux: vcore-gpio-pmux {
> + groups = "SM_GPIO5";
> + function = "gpio";
> + };
> +};
> +
> +&sm_uart0 {
> + status = "okay";
> +};
> +
> +&sm_i2c0 {
> + status = "okay";
> + pinctrl-names = "default";
> + pinctrl-0 = <&sm_i2c0_pmux>;
> + clock-frequency = <100000>;
> +
> + expander0: gpio@43 {
> + compatible = "fcs,fxl6408";
> + reg = <0x43>;
> + gpio-controller;
> + #gpio-cells = <2>;
> + };
> +
> + expander1: gpio@44 {
> + compatible = "fcs,fxl6408";
> + reg = <0x44>;
> + gpio-controller;
> + #gpio-cells = <2>;
> + };
> +};
> +
> +&sm_i2c1 {
> + status = "okay";
> + pinctrl-names = "default";
> + pinctrl-0 = <&sm_i2c1_pmux>;
> + clock-frequency = <100000>;
> +
> + vcore: regulator@60 {
> + compatible = "silergy,sy8827n";
> + reg = <0x60>;
> + regulator-name = "vcore";
> + regulator-min-microvolt = <700000>;
> + regulator-max-microvolt = <987500>;
> + regulator-always-on;
> + regulator-boot-on;
> + regulator-active-discharge = <0>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&vcore_gpio_pmux>;
> + enable-gpios = <&portc 5 GPIO_ACTIVE_LOW>;
> + };
> +};
> +
> +&soc_i2c0 {
> + status = "okay";
> + pinctrl-names = "default";
> + pinctrl-0 = <&soc_i2c0_pmux>;
> + clock-frequency = <100000>;
> +};
> +
> +&sm_uart1 {
> + status = "okay";
> +};
next prev parent reply other threads:[~2026-11-19 9:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 10:23 [PATCH v2 00/13] arm64: add Synaptics SL2610 SoCs and " Jisheng Zhang
2026-11-15 10:23 ` [PATCH v2 01/13] arm64: kconfig: let ARCH_BERLIN cover Synaptics arm64 SoCs Jisheng Zhang
2026-11-15 10:23 ` [PATCH v2 02/13] pinctrl: berlin: use u16 instead of u8 for the offset Jisheng Zhang
2026-11-15 10:23 ` [PATCH v2 03/13] pinctrl: berlin: enable module build support Jisheng Zhang
2026-11-15 10:23 ` [PATCH v2 04/13] pinctrl: berlin: add optional pinconf support Jisheng Zhang
2026-11-15 10:23 ` [PATCH v2 05/13] dt-bindings: soc: synaptics: add SL2610 system controllers Jisheng Zhang
2026-11-15 10:23 ` [PATCH v2 06/13] soc: synaptics: add SL2610 system controller support Jisheng Zhang
2026-11-15 10:23 ` [PATCH v2 07/13] reset: add Synaptics SL2610 reset " Jisheng Zhang
2026-11-16 11:49 ` Philipp Zabel
2026-11-16 12:05 ` Philipp Zabel
2026-11-15 10:23 ` [PATCH v2 08/13] pinctrl: berlin: add Synaptics SL2610 pin " Jisheng Zhang
2026-11-16 12:08 ` Jisheng Zhang
2026-11-15 10:23 ` [PATCH v2 09/13] clk: berlin: add Synaptics clock controller helpers Jisheng Zhang
2026-11-15 10:23 ` [PATCH v2 10/13] clk: berlin: add Synaptics SL2610 clocks and PLLs Jisheng Zhang
2026-11-15 10:23 ` [PATCH v2 11/13] dt-bindings: arm: berlin: add Synaptics SL2610 SoCs and RDK boards Jisheng Zhang
2026-11-15 10:23 ` [PATCH v2 12/13] arm64: dts: synaptics: add SL2610 family SoCs Jisheng Zhang
2026-11-15 10:23 ` [PATCH v2 13/13] arm64: dts: synaptics: add SL2610 family RDK boards Jisheng Zhang
2026-11-19 9:23 ` Richard GENOUD [this message]
2026-11-16 12:06 ` [PATCH v2 00/13] arm64: add Synaptics SL2610 SoCs and " Jisheng Zhang
2026-11-18 7:54 ` Richard GENOUD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53f65c05-1c09-410d-8f49-9175f46a0609@bootlin.com \
--to=richard.genoud@bootlin.com \
--cc=bmasney+clk@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet+clk@baylibre.com \
--cc=jszhang@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®