* [PATCH v2 1/5] dt-bindings: soc: samsung: exynos-sysreg: Add compatibles for Exynos5515
2026-10-19 10:23 [PATCH v2 0/5] arm64: dts: exynos: add initial support for Samsung Galaxy Watch FE Aiden Isik via B4 Relay
@ 2026-10-19 10:23 ` Aiden Isik via B4 Relay
2026-10-19 10:23 ` [PATCH v2 2/5] dt-bindings: soc: samsung: exynos-pmu: Add Exynos5515 compatible Aiden Isik via B4 Relay
` (4 subsequent siblings)
5 siblings, 0 replies; 10+ messages in thread
From: Aiden Isik via B4 Relay @ 2026-10-19 10:23 UTC (permalink / raw)
To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Peter Griffin,
Alim Akhtar
Cc: Krzysztof Kozlowski, devicetree, linux-arm-kernel,
linux-samsung-soc, linux-kernel, Aiden Isik
From: Aiden Isik <aidenisik@member.fsf.org>
Add Exynos5515 compatibles for the following sysreg controllers:
- top
- peri
- fsys
Signed-off-by: Aiden Isik <aidenisik@member.fsf.org>
---
.../devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml b/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml
index fcdb9ffd2644..c6731a3ea1c4 100644
--- a/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml
+++ b/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml
@@ -29,6 +29,9 @@ properties:
- samsung,exynos3-sysreg
- samsung,exynos4-sysreg
- samsung,exynos5-sysreg
+ - samsung,exynos5515-fsys-sysreg
+ - samsung,exynos5515-peri-sysreg
+ - samsung,exynos5515-top-sysreg
- samsung,exynos7870-cam0-sysreg
- samsung,exynos7870-disp-sysreg
- samsung,exynos8895-fsys0-sysreg
--
2.54.0
^ permalink raw reply [flat|nested] 10+ messages in thread* [PATCH v2 2/5] dt-bindings: soc: samsung: exynos-pmu: Add Exynos5515 compatible
2026-10-19 10:23 [PATCH v2 0/5] arm64: dts: exynos: add initial support for Samsung Galaxy Watch FE Aiden Isik via B4 Relay
2026-10-19 10:23 ` [PATCH v2 1/5] dt-bindings: soc: samsung: exynos-sysreg: Add compatibles for Exynos5515 Aiden Isik via B4 Relay
@ 2026-10-19 10:23 ` Aiden Isik via B4 Relay
2026-10-19 10:23 ` [PATCH v2 3/5] dt-bindings: arm: samsung: Add lucky7 board binding Aiden Isik via B4 Relay
` (3 subsequent siblings)
5 siblings, 0 replies; 10+ messages in thread
From: Aiden Isik via B4 Relay @ 2026-10-19 10:23 UTC (permalink / raw)
To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Peter Griffin,
Alim Akhtar
Cc: Krzysztof Kozlowski, devicetree, linux-arm-kernel,
linux-samsung-soc, linux-kernel, Aiden Isik
From: Aiden Isik <aidenisik@member.fsf.org>
Add exynos5515-pmu compatible to the device tree bindings documentation.
Use the samsung,exynos7-pmu compatible, as it works the same for Exynos7
and Exynos5515.
Signed-off-by: Aiden Isik <aidenisik@member.fsf.org>
---
Documentation/devicetree/bindings/soc/samsung/exynos-pmu.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/soc/samsung/exynos-pmu.yaml b/Documentation/devicetree/bindings/soc/samsung/exynos-pmu.yaml
index 5bd39876e3b3..1a0d9de79696 100644
--- a/Documentation/devicetree/bindings/soc/samsung/exynos-pmu.yaml
+++ b/Documentation/devicetree/bindings/soc/samsung/exynos-pmu.yaml
@@ -33,6 +33,7 @@ properties:
- enum:
- axis,artpec9-pmu
- samsung,exynos2200-pmu
+ - samsung,exynos5515-pmu
- samsung,exynos7870-pmu
- samsung,exynos7885-pmu
- samsung,exynos8890-pmu
--
2.54.0
^ permalink raw reply [flat|nested] 10+ messages in thread* [PATCH v2 3/5] dt-bindings: arm: samsung: Add lucky7 board binding
2026-10-19 10:23 [PATCH v2 0/5] arm64: dts: exynos: add initial support for Samsung Galaxy Watch FE Aiden Isik via B4 Relay
2026-10-19 10:23 ` [PATCH v2 1/5] dt-bindings: soc: samsung: exynos-sysreg: Add compatibles for Exynos5515 Aiden Isik via B4 Relay
2026-10-19 10:23 ` [PATCH v2 2/5] dt-bindings: soc: samsung: exynos-pmu: Add Exynos5515 compatible Aiden Isik via B4 Relay
@ 2026-10-19 10:23 ` Aiden Isik via B4 Relay
2026-10-19 10:23 ` [PATCH v2 4/5] arm64: dts: exynos: Add initial support for Exynos5515 SoC Aiden Isik via B4 Relay
` (2 subsequent siblings)
5 siblings, 0 replies; 10+ messages in thread
From: Aiden Isik via B4 Relay @ 2026-10-19 10:23 UTC (permalink / raw)
To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Peter Griffin,
Alim Akhtar
Cc: Krzysztof Kozlowski, devicetree, linux-arm-kernel,
linux-samsung-soc, linux-kernel, Aiden Isik
From: Aiden Isik <aidenisik@member.fsf.org>
Add device tree binding for the Samsung Galaxy Watch FE (SM-R861/SM-R866)
board, based on the Exynos5515 SoC.
Signed-off-by: Aiden Isik <aidenisik@member.fsf.org>
---
Documentation/devicetree/bindings/arm/samsung/samsung-boards.yaml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/samsung/samsung-boards.yaml b/Documentation/devicetree/bindings/arm/samsung/samsung-boards.yaml
index db19a686f490..c80fac4fad7a 100644
--- a/Documentation/devicetree/bindings/arm/samsung/samsung-boards.yaml
+++ b/Documentation/devicetree/bindings/arm/samsung/samsung-boards.yaml
@@ -157,6 +157,12 @@ properties:
- const: samsung,exynos5420
- const: samsung,exynos5
+ - description: Exynos5515 based boards
+ items:
+ - enum:
+ - samsung,lucky7 # Samsung Galaxy Watch FE (SM-R861/SM-R866)
+ - const: samsung,exynos5515
+
- description: Google Peach Pit Boards (Rev 6+)
items:
- const: google,pit-rev16
--
2.54.0
^ permalink raw reply [flat|nested] 10+ messages in thread* [PATCH v2 4/5] arm64: dts: exynos: Add initial support for Exynos5515 SoC
2026-10-19 10:23 [PATCH v2 0/5] arm64: dts: exynos: add initial support for Samsung Galaxy Watch FE Aiden Isik via B4 Relay
` (2 preceding siblings ...)
2026-10-19 10:23 ` [PATCH v2 3/5] dt-bindings: arm: samsung: Add lucky7 board binding Aiden Isik via B4 Relay
@ 2026-10-19 10:23 ` Aiden Isik via B4 Relay
2026-10-19 10:23 ` [PATCH v2 5/5] arm64: dts: exynos: Add initial support for Samsung Galaxy Watch FE Aiden Isik via B4 Relay
2026-10-20 7:53 ` [PATCH v2 0/5] arm64: dts: exynos: add " Krzysztof Kozlowski
5 siblings, 0 replies; 10+ messages in thread
From: Aiden Isik via B4 Relay @ 2026-10-19 10:23 UTC (permalink / raw)
To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Peter Griffin,
Alim Akhtar
Cc: Krzysztof Kozlowski, devicetree, linux-arm-kernel,
linux-samsung-soc, linux-kernel, Aiden Isik
From: Aiden Isik <aidenisik@member.fsf.org>
The Exynos5515 is an ARMv8 wearable SoC, used in the following devices:
- Samsung Galaxy Watch 4 (SM-R860/SM-R865/SM-R870/SM-R875)
- Samsung Galaxy Watch 4 Classic (SM-R880/SM-R885/SM-R890/SM-R895)
- Samsung Galaxy Watch FE (SM-R861/SM-R866)
- Samsung Galaxy Watch 5 (SM-R900/SM-R905/SM-R910/SM-R915)
- Samsung Galaxy Watch 5 Pro (SM-R920/SM-R925)
- Samsung Galaxy Watch 6 (SM-R930/SM-R935/SM-R940/SM-R945)
- Samsung Galaxy Watch 6 Classic (SM-R950/SM-R955/SM-R960/SM-R965)
Add the following support for this SoC:
- Both Cortex-A55 cores
- ChipID
- Generic timer
- Watchdog timer
- CMU_TOP, CMU_PERI, and CMU_FSYS clock management units
The devices using this SoC suffer from the same issue as many other
Samsung devices, where the stock bootloader does not configure CNTFRQ_EL0.
To mitigate this, the correct frequency is hardcoded in the timer node.
The VGIC maintenance interrupt on this SoC is also unavailable.
Signed-off-by: Aiden Isik <aidenisik@member.fsf.org>
---
arch/arm64/boot/dts/exynos/exynos5515.dtsi | 189 +++++++++++++++++++++++++++++
1 file changed, 189 insertions(+)
diff --git a/arch/arm64/boot/dts/exynos/exynos5515.dtsi b/arch/arm64/boot/dts/exynos/exynos5515.dtsi
new file mode 100644
index 000000000000..ce6fcbfffdb2
--- /dev/null
+++ b/arch/arm64/boot/dts/exynos/exynos5515.dtsi
@@ -0,0 +1,189 @@
+// SPDX-License-Identifier: GPL-2.0-or-later
+/*
+ * Samsung Exynos 5515 SoC device tree source
+ *
+ * Copyright (c) 2026 Aiden Isik <aidenisik+git@member.fsf.org>
+ */
+
+#include <dt-bindings/clock/samsung,exynos5515-cmu.h>
+#include <dt-bindings/interrupt-controller/arm-gic.h>
+
+/ {
+ compatible = "samsung,exynos5515";
+ #address-cells = <2>;
+ interrupt-parent = <&gic>;
+ #size-cells = <1>;
+
+ cpus {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ cpu-map {
+ cluster0 {
+ core0 {
+ cpu = <&cpu0>;
+ };
+
+ core1 {
+ cpu = <&cpu1>;
+ };
+ };
+ };
+
+ cpu0: cpu@0 {
+ device_type = "cpu";
+ compatible = "arm,cortex-a55";
+ reg = <0x0>;
+ enable-method = "psci";
+ };
+
+ cpu1: cpu@100 {
+ device_type = "cpu";
+ compatible = "arm,cortex-a55";
+ reg = <0x100>;
+ enable-method = "psci";
+ };
+ };
+
+ oscclk: osc-clock {
+ compatible = "fixed-clock";
+ #clock-cells = <0>;
+ clock-output-names = "oscclk";
+ };
+
+ pmu {
+ compatible = "arm,armv8-pmuv3";
+ interrupt-affinity = <&cpu0>,
+ <&cpu1>;
+ interrupts = <GIC_SPI 99 IRQ_TYPE_LEVEL_HIGH>,
+ <GIC_SPI 100 IRQ_TYPE_LEVEL_HIGH>;
+ };
+
+ psci {
+ compatible = "arm,psci-1.0";
+ method = "smc";
+ };
+
+ soc: soc@0 {
+ compatible = "simple-bus";
+ ranges = <0x0 0x0 0x0 0x20000000>;
+
+ #address-cells = <1>;
+ #size-cells = <1>;
+
+ chipid@10000000 {
+ compatible = "samsung,exynos5515-chipid",
+ "samsung,exynos850-chipid";
+ reg = <0x10000000 0x100>;
+ };
+
+ sysreg_peri: syscon@10020000 {
+ compatible = "samsung,exynos5515-peri-sysreg", "syscon";
+ reg = <0x10020000 0x10000>;
+ };
+
+ cmu_peri: clock-controller@10030000 {
+ compatible = "samsung,exynos5515-cmu-peri";
+ reg = <0x10030000 0x10000>;
+ #clock-cells = <1>;
+ clocks = <&oscclk>,
+ <&cmu_top CLK_DOUT_CMU_PERI_BUS>,
+ <&cmu_top CLK_DOUT_CMU_PERI_IP>,
+ <&cmu_top CLK_DOUT_CMU_PERI_UART>;
+ clock-names = "oscclk",
+ "bus",
+ "ip",
+ "uart";
+ samsung,sysreg = <&sysreg_peri>;
+ };
+
+ watchdog: watchdog@10050000 {
+ compatible = "samsung,exynos5515-wdt";
+ reg = <0x10050000 0x100>;
+ clocks = <&cmu_peri CLK_GOUT_PERI_WDT0_PCLK>,
+ <&oscclk>;
+ clock-names = "watchdog",
+ "watchdog_src";
+ interrupts = <GIC_SPI 185 IRQ_TYPE_LEVEL_HIGH>;
+ samsung,syscon-phandle = <&pmu_system_controller>;
+
+ status = "disabled";
+ };
+
+ cmu_fsys: clock-controller@10400000 {
+ compatible = "samsung,exynos5515-cmu-fsys";
+ reg = <0x10400000 0x10000>;
+ #clock-cells = <1>;
+ clocks = <&oscclk>,
+ <&cmu_top CLK_DOUT_CMU_FSYS_BUS>,
+ <&cmu_top CLK_DOUT_CMU_FSYS_MMC_CARD>,
+ <&cmu_top CLK_DOUT_CMU_FSYS_MMC_EMBD>,
+ <&cmu_top CLK_DOUT_CMU_FSYS_USB20DRD>;
+ clock-names = "oscclk",
+ "bus",
+ "mmc_card",
+ "mmc_embd",
+ "usb20drd";
+ samsung,sysreg = <&sysreg_fsys>;
+ };
+
+ sysreg_fsys: syscon@10420000 {
+ compatible = "samsung,exynos5515-fsys-sysreg", "syscon";
+ reg = <0x10420000 0x10000>;
+ };
+
+ pmu_system_controller: system-controller@12860000 {
+ compatible = "samsung,exynos5515-pmu",
+ "samsung,exynos7-pmu",
+ "syscon";
+ reg = <0x12860000 0x10000>;
+ };
+
+ cmu_top: clock-controller@15410000 {
+ compatible = "samsung,exynos5515-cmu-top";
+ reg = <0x15410000 0x10000>;
+ #clock-cells = <1>;
+ clocks = <&oscclk>;
+ clock-names = "oscclk";
+ samsung,sysreg = <&sysreg_top>;
+ };
+
+ sysreg_top: syscon@15430000 {
+ compatible = "samsung,exynos5515-top-sysreg", "syscon";
+ reg = <0x15430000 0x10000>;
+ };
+
+ gic: interrupt-controller@15601000 {
+ compatible = "arm,gic-400";
+ reg = <0x15601000 0x1000>,
+ <0x15602000 0x2000>,
+ <0x15604000 0x2000>,
+ <0x15606000 0x2000>;
+ #address-cells = <0>;
+ #interrupt-cells = <3>;
+ interrupt-controller;
+ /* VGIC maintenance interrupt is not available */
+ };
+ };
+
+ timer {
+ compatible = "arm,armv8-timer";
+ /*
+ * Non-updatable, broken stock Samsung bootloader does not
+ * configure CNTFRQ_EL0
+ */
+ clock-frequency = <26000000>;
+ interrupts = <GIC_PPI 13
+ (GIC_CPU_MASK_SIMPLE(8) | IRQ_TYPE_LEVEL_LOW)>,
+ <GIC_PPI 14
+ (GIC_CPU_MASK_SIMPLE(8) | IRQ_TYPE_LEVEL_LOW)>,
+ <GIC_PPI 11
+ (GIC_CPU_MASK_SIMPLE(8) | IRQ_TYPE_LEVEL_LOW)>,
+ <GIC_PPI 10
+ (GIC_CPU_MASK_SIMPLE(8) | IRQ_TYPE_LEVEL_LOW)>,
+ <GIC_PPI 12
+ (GIC_CPU_MASK_SIMPLE(8) | IRQ_TYPE_LEVEL_LOW)>;
+ };
+};
+
+#include "arm/samsung/exynos-syscon-restart.dtsi"
--
2.54.0
^ permalink raw reply [flat|nested] 10+ messages in thread* [PATCH v2 5/5] arm64: dts: exynos: Add initial support for Samsung Galaxy Watch FE
2026-10-19 10:23 [PATCH v2 0/5] arm64: dts: exynos: add initial support for Samsung Galaxy Watch FE Aiden Isik via B4 Relay
` (3 preceding siblings ...)
2026-10-19 10:23 ` [PATCH v2 4/5] arm64: dts: exynos: Add initial support for Exynos5515 SoC Aiden Isik via B4 Relay
@ 2026-10-19 10:23 ` Aiden Isik via B4 Relay
2026-10-20 7:53 ` [PATCH v2 0/5] arm64: dts: exynos: add " Krzysztof Kozlowski
5 siblings, 0 replies; 10+ messages in thread
From: Aiden Isik via B4 Relay @ 2026-10-19 10:23 UTC (permalink / raw)
To: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Peter Griffin,
Alim Akhtar
Cc: Krzysztof Kozlowski, devicetree, linux-arm-kernel,
linux-samsung-soc, linux-kernel, Aiden Isik
From: Aiden Isik <aidenisik@member.fsf.org>
The Samsung Galaxy Watch FE (SM-R861/SM-R866), codenamed lucky7, is a
smartwatch developed by Samsung and released in 2024. It has 1.5GiB RAM,
16GiB of eMMC storage, an Exynos5515 (W920) SoC, and a 396x396 display.
Support for the following is added by this device tree:
- Bootloader framebuffer
- Memory
Signed-off-by: Aiden Isik <aidenisik@member.fsf.org>
---
arch/arm64/boot/dts/exynos/exynos5515-lucky7.dts | 219 +++++++++++++++++++++++
1 file changed, 219 insertions(+)
diff --git a/arch/arm64/boot/dts/exynos/exynos5515-lucky7.dts b/arch/arm64/boot/dts/exynos/exynos5515-lucky7.dts
new file mode 100644
index 000000000000..e80a0f0948cb
--- /dev/null
+++ b/arch/arm64/boot/dts/exynos/exynos5515-lucky7.dts
@@ -0,0 +1,219 @@
+// SPDX-License-Identifier: GPL-2.0-or-later
+/*
+ * Samsung Galaxy Watch FE (lucky7/SM-R861/SM-R866) device tree source
+ *
+ * Copyright (c) 2026 Aiden Isik <aidenisik+git@member.fsf.org>
+ */
+
+/dts-v1/;
+#include "exynos5515.dtsi"
+
+/ {
+ compatible = "samsung,lucky7", "samsung,exynos5515";
+ chassis-type = "watch";
+ model = "Samsung Galaxy Watch FE (SM-R861/SM-R866)";
+
+ chosen {
+ ranges;
+ #address-cells = <2>;
+ #size-cells = <1>;
+
+ framebuffer@9e0cf000 {
+ compatible = "simple-framebuffer";
+ reg = <0x0 0x9e0cf000 (396 * 396 * 4)>;
+ format = "a8r8g8b8";
+ height = <396>;
+ stride = <(396 * 4)>;
+ width = <396>;
+ };
+ };
+
+ memory@80000000 {
+ device_type = "memory";
+ reg = <0x0 0x80000000 0x3ea00000>,
+ <0x0 0xc0000000 0x20000000>;
+ };
+
+ reserved-memory {
+ ranges;
+ #address-cells = <2>;
+ #size-cells = <1>;
+
+ /*
+ * Some of these misc-rmem regions belong to memory-mapped
+ * devices, and will be assigned to drivers as support
+ * is added.
+ *
+ * Other regions belong to the TrustZone firmware and should
+ * never be touched.
+ */
+ misc-rmem@87000000 {
+ reg = <0x0 0x87000000 0x200000>;
+ no-map;
+ };
+
+ misc-rmem@87fff000 {
+ reg = <0x0 0x87fff000 0x1000>;
+ no-map;
+ };
+
+ misc-rmem@8a000000 {
+ reg = <0x0 0x8a000000 0x31000>;
+ no-map;
+ };
+
+ misc-rmem@8d800000 {
+ reg = <0x0 0x8d800000 0x180000>;
+ no-map;
+ };
+
+ misc-rmem@8ffff000 {
+ reg = <0x0 0x8ffff000 0x33000>;
+ no-map;
+ };
+
+ misc-rmem@90100000 {
+ reg = <0x0 0x90100000 0x200000>;
+ no-map;
+ };
+
+ misc-rmem@98a00000 {
+ reg = <0x0 0x98a00000 0x600000>;
+ no-map;
+ };
+
+ misc-rmem@9a000000 {
+ reg = <0x0 0x9a000000 0xc00000>;
+ no-map;
+ };
+
+ misc-rmem@9b000000 {
+ reg = <0x0 0x9b000000 0x400000>;
+ no-map;
+ };
+
+ misc-rmem@9bd00000 {
+ reg = <0x0 0x9bd00000 0x208000>;
+ no-map;
+ };
+
+ misc-rmem@9c000000 {
+ reg = <0x0 0x9c000000 0x20000>;
+ no-map;
+ };
+
+ framebuffer@9e0cf000 {
+ /*
+ * Reserve up to the end of the final page of the
+ * framebuffer region, to prevent memory aliasing.
+ *
+ * size: align((396 * 396 * 4), 0x1000)
+ */
+ reg = <0x0 0x9e0cf000 0x9a000>;
+ no-map;
+ };
+
+ misc-rmem@a0000000 {
+ reg = <0x0 0xa0000000 0x10000>;
+ no-map;
+ };
+
+ misc-rmem@a0010000 {
+ reg = <0x0 0xa0010000 0x400000>;
+ no-map;
+ };
+
+ misc-rmem@a0510000 {
+ reg = <0x0 0xa0510000 0x1000>;
+ no-map;
+ };
+
+ misc-rmem@a0900000 {
+ reg = <0x0 0xa0900000 0x2000>;
+ no-map;
+ };
+
+ misc-rmem@a0902000 {
+ reg = <0x0 0xa0902000 0x1000>;
+ no-map;
+ };
+
+ misc-rmem@a0910000 {
+ reg = <0x0 0xa0910000 0x3c000>;
+ no-map;
+ };
+
+ misc-rmem@b0000000 {
+ reg = <0x0 0xb0000000 0x200000>;
+ no-map;
+ };
+
+ misc-rmem@b1000000 {
+ reg = <0x0 0xb1000000 0x200000>;
+ no-map;
+ };
+
+ misc-rmem@bbfff000 {
+ reg = <0x0 0xbbfff000 0x1000000>;
+ no-map;
+ };
+
+ misc-rmem@bcfff000 {
+ reg = <0x0 0xbcfff000 0x1000>;
+ no-map;
+ };
+
+ misc-rmem@bd430000 {
+ reg = <0x0 0xbd430000 0x1250000>;
+ no-map;
+ };
+
+ misc-rmem@d0000000 {
+ reg = <0x0 0xd0000000 0x5d00000>;
+ no-map;
+ };
+
+ misc-rmem@dc444000 {
+ reg = <0x0 0xdc444000 0x2bbc000>;
+ no-map;
+ };
+
+ misc-rmem@df005000 {
+ reg = <0x0 0xdf005000 0x1000>;
+ no-map;
+ };
+
+ misc-rmem@df008000 {
+ reg = <0x0 0xdf008000 0x1000>;
+ no-map;
+ };
+
+ misc-rmem@df009000 {
+ reg = <0x0 0xdf009000 0x12000>;
+ no-map;
+ };
+
+ misc-rmem@df01b000 {
+ reg = <0x0 0xdf01b000 0x21000>;
+ no-map;
+ };
+
+ misc-rmem@df03c000 {
+ reg = <0x0 0xdf03c000 0x1000>;
+ no-map;
+ };
+
+ misc-rmem@df03d000 {
+ reg = <0x0 0xdf03d000 0xfc3000>;
+ no-map;
+ };
+ };
+};
+
+&oscclk {
+ clock-frequency = <26000000>;
+};
+
+&watchdog {
+ status = "okay";
+};
--
2.54.0
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [PATCH v2 0/5] arm64: dts: exynos: add initial support for Samsung Galaxy Watch FE
2026-10-19 10:23 [PATCH v2 0/5] arm64: dts: exynos: add initial support for Samsung Galaxy Watch FE Aiden Isik via B4 Relay
` (4 preceding siblings ...)
2026-10-19 10:23 ` [PATCH v2 5/5] arm64: dts: exynos: Add initial support for Samsung Galaxy Watch FE Aiden Isik via B4 Relay
@ 2026-10-20 7:53 ` Krzysztof Kozlowski
2026-10-20 10:27 ` Aiden Isik
5 siblings, 1 reply; 10+ messages in thread
From: Krzysztof Kozlowski @ 2026-10-20 7:53 UTC (permalink / raw)
To: Aiden Isik
Cc: Rob Herring, Krzysztof Kozlowski, Conor Dooley, Peter Griffin,
Alim Akhtar, devicetree, linux-arm-kernel, linux-samsung-soc,
linux-kernel
On Mon, Oct 19, 2026 at 11:23:46AM +0100, Aiden Isik wrote:
> Hi there,
>
> This patchset adds initial support for the Exynos5515 SoC, along with
> support for the Samsung Galaxy Watch FE (codenamed lucky7), which uses
> this SoC.
>
> Support for the following is added:
> - Bootloader framebuffer
> - Both CPU cores
> - Memory
> - Generic timer
> - Watchdog timer
> - CMU_TOP, CMU_FSYS, CMU_PERI clock management units
> - ChipID
>
> Currently, these device trees support booting the device to an initramfs.
>
> There are quite a few regions of reserved memory, where usage of them
> can crash the system and/or cause unexpected behaviour. Currently, most
> of them are named "misc-rmem@addr". They will be given names as their
> accompanying device drivers are added and their purpose becomes apparent.
> If you would like them named feel differently, feel free to let me know.
>
> The VGIC maintenance interrupt seems to be unavailable on this SoC.
> I cannot find any reference to it, nor usage of it, anywhere.
> It *could* very well still exist, but it is a mystery for now (and also
> not a *huge* deal on a low-power SoC designed for smartwatches).
>
> I am getting checkpatch warnings on this patchset advising to check
> MAINTAINERS as new files were added, but I am ignoring them as the
> entirety of arch/arm64/boot/dts/exynos is covered already.
>
> This patchset depends on [1] for drivers and device tree bindings.
> Note: This dependency was merged into the linux-watchdog tree.
DTS cannot depend on drivers. Please fix your code, to avoid that.
Dropping from my queue.
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [PATCH v2 0/5] arm64: dts: exynos: add initial support for Samsung Galaxy Watch FE
2026-10-20 7:53 ` [PATCH v2 0/5] arm64: dts: exynos: add " Krzysztof Kozlowski
@ 2026-10-20 10:27 ` Aiden Isik
2026-10-20 10:42 ` Aiden Isik
0 siblings, 1 reply; 10+ messages in thread
From: Aiden Isik @ 2026-10-20 10:27 UTC (permalink / raw)
To: Krzysztof Kozlowski
Cc: Aiden Isik, Rob Herring, Krzysztof Kozlowski, Conor Dooley,
Peter Griffin, Alim Akhtar, devicetree, linux-arm-kernel,
linux-samsung-soc, linux-kernel
Hi Krzysztof,
> DTS cannot depend on drivers. Please fix your code, to avoid that.
> Dropping from my queue.
What exactly do you mean by this? The DTS describes the
hardware in the system, which requires drivers to drive it.
Is it a wording issue? I don't depend on actual driver code in the DTS,
only bindings for the hardware they drive, so maybe I could make
that more clear?
Kind regards,
- Aiden Isik
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v2 0/5] arm64: dts: exynos: add initial support for Samsung Galaxy Watch FE
2026-10-20 10:27 ` Aiden Isik
@ 2026-10-20 10:42 ` Aiden Isik
2026-10-20 11:20 ` Krzysztof Kozlowski
0 siblings, 1 reply; 10+ messages in thread
From: Aiden Isik @ 2026-10-20 10:42 UTC (permalink / raw)
To: Aiden Isik
Cc: Krzysztof Kozlowski, Aiden Isik, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Peter Griffin, Alim Akhtar,
devicetree, linux-arm-kernel, linux-samsung-soc, linux-kernel
> Is it a wording issue? I don't depend on actual driver code in the DTS,
> only bindings for the hardware they drive, so maybe I could make
> that more clear?
To elaborate on this, I listed that as a dependency because that patch adds
the compatible string for the watchdog timer, and I was also under the
impression that drivers must be already in-tree before a DTS patch which
uses the hardware the drivers support can be applied (otherwise you
would be merging a DTS of which parts do not work as the prerequisite
drivers are not in the kernel).
Is this not the case?
Kind regards,
- Aiden Isik
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH v2 0/5] arm64: dts: exynos: add initial support for Samsung Galaxy Watch FE
2026-10-20 10:42 ` Aiden Isik
@ 2026-10-20 11:20 ` Krzysztof Kozlowski
0 siblings, 0 replies; 10+ messages in thread
From: Krzysztof Kozlowski @ 2026-10-20 11:20 UTC (permalink / raw)
To: Aiden Isik
Cc: Aiden Isik, Rob Herring, Krzysztof Kozlowski, Conor Dooley,
Peter Griffin, Alim Akhtar, devicetree, linux-arm-kernel,
linux-samsung-soc, linux-kernel
On 20/10/2026 12:42, Aiden Isik wrote:
>> Is it a wording issue? I don't depend on actual driver code in the DTS,
>> only bindings for the hardware they drive, so maybe I could make
>> that more clear?
>
> To elaborate on this, I listed that as a dependency because that patch adds
> the compatible string for the watchdog timer, and I was also under the
> impression that drivers must be already in-tree before a DTS patch which
> uses the hardware the drivers support can be applied (otherwise you
> would be merging a DTS of which parts do not work as the prerequisite
> drivers are not in the kernel).
>
> Is this not the case?
That was never the case. See maintainer soc profiles.
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 10+ messages in thread