[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240125140139.3616119-2-andre.draszik@linaro.org>
Date: Thu, 25 Jan 2024 14:01:39 +0000
From: André Draszik <andre.draszik@...aro.org>
To: linux-kernel@...r.kernel.org,
robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org,
conor+dt@...nel.org,
alim.akhtar@...sung.com,
peter.griffin@...aro.org
Cc: kernel-team@...roid.com,
tudor.ambarus@...aro.org,
willmcvicker@...gle.com,
daniel.lezcano@...aro.org,
tglx@...utronix.de,
devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org
Subject: [PATCH 2/2] arm64: dts: exynos: gs101: sysreg_peric1 needs a clock
Without the clock running, we can not access its registers, and now
that we have it, we should add it here so that it gets enabled as
and when needed.
Update the DTSI accordingly.
Signed-off-by: André Draszik <andre.draszik@...aro.org>
---
arch/arm64/boot/dts/exynos/google/gs101.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/exynos/google/gs101.dtsi b/arch/arm64/boot/dts/exynos/google/gs101.dtsi
index 412d2866dca7..aaac04df5e65 100644
--- a/arch/arm64/boot/dts/exynos/google/gs101.dtsi
+++ b/arch/arm64/boot/dts/exynos/google/gs101.dtsi
@@ -364,6 +364,7 @@ cmu_peric0: clock-controller@...00000 {
sysreg_peric0: syscon@...20000 {
compatible = "google,gs101-peric0-sysreg", "syscon";
reg = <0x10820000 0x10000>;
+ clocks = <&cmu_peric0 CLK_GOUT_PERIC0_SYSREG_PERIC0_PCLK>;
};
pinctrl_peric0: pinctrl@...40000 {
--
2.43.0.429.g432eaa2c6b-goog
Powered by blists - more mailing lists