.. otherwise it won't be accessible.
Update the schema to make this obvious.
Signed-off-by: André Draszik <[email protected]>
---
.../devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml b/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml
index 1794e3799f21..33d837ae4f45 100644
--- a/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml
+++ b/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml
@@ -72,6 +72,7 @@ allOf:
compatible:
contains:
enum:
+ - google,gs101-peric0-sysreg
- samsung,exynos850-cmgp-sysreg
- samsung,exynos850-peri-sysreg
- samsung,exynos850-sysreg
--
2.43.0.429.g432eaa2c6b-goog
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 <[email protected]>
---
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@10800000 {
sysreg_peric0: syscon@10820000 {
compatible = "google,gs101-peric0-sysreg", "syscon";
reg = <0x10820000 0x10000>;
+ clocks = <&cmu_peric0 CLK_GOUT_PERIC0_SYSREG_PERIC0_PCLK>;
};
pinctrl_peric0: pinctrl@10840000 {
--
2.43.0.429.g432eaa2c6b-goog
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 <[email protected]>
---
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@10800000 {
sysreg_peric0: syscon@10820000 {
compatible = "google,gs101-peric0-sysreg", "syscon";
reg = <0x10820000 0x10000>;
+ clocks = <&cmu_peric0 CLK_GOUT_PERIC0_SYSREG_PERIC0_PCLK>;
};
pinctrl_peric0: pinctrl@10840000 {
--
2.43.0.429.g432eaa2c6b-goog
> [PATCH v2] arm64: dts: exynos: gs101: sysreg_peric0 needs a clock
Sorry for copy/paste error in the subject :-(
I've sent an update in https://lore.kernel.org/all/[email protected]/
Cheers,
Andre'
On 25/01/2024 15:10, André Draszik wrote:
>> [PATCH v2] arm64: dts: exynos: gs101: sysreg_peric0 needs a clock
>
> Sorry for copy/paste error in the subject :-(
>
> I've sent an update in https://lore.kernel.org/all/[email protected]/
Which makes it impossible to apply (at least with usual workflow):
Grabbing thread from
lore.kernel.org/all/[email protected]/t.mbox.gz
Checking for newer revisions
Grabbing search results from lore.kernel.org
Analyzing 4 messages in the thread
Will use the latest revision: v2
You can pick other revisions using the -vN flag
Checking attestation on all messages, may take a moment...
---
✓ [PATCH v2] arm64: dts: exynos: gs101: sysreg_peric0 needs a clock
+ Link:
https://lore.kernel.org/r/[email protected]
+ Signed-off-by: Krzysztof Kozlowski <[email protected]>
---
✓ Signed: DKIM/linaro.org
---
Total patches: 1
---
Applying: arm64: dts: exynos: gs101: sysreg_peric0 needs a clock
---
Patchwork: setting state on patchwork.kernel.org/linux-samsung-soc
-> under-review : [v2] arm64: dts: exynos: gs101: sysreg_peric0 needs a
clock
Please do not invent your own workflows of handling patches. Each
submission must be:
1. In separate thread, not linked to something else,
2. Complete.
I await for v3.
Best regards,
Krzysztof