From: "André Draszik" <andre.draszik@linaro.org>
To: Sebastian Reichel <sre@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>
Cc: "Peter Griffin" <peter.griffin@linaro.org>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Will McVicker" <willmcvicker@google.com>,
kernel-team@android.com, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
"André Draszik" <andre.draszik@linaro.org>
Subject: [PATCH v4 2/3] dt-bindings: soc: samsung: exynos-pmu: update reset for gs101
Date: Fri, 28 Mar 2025 15:15:20 +0000 [thread overview]
Message-ID: <20250328-syscon-reboot-reset-mode-v4-2-77ba57703ace@linaro.org> (raw)
In-Reply-To: <20250328-syscon-reboot-reset-mode-v4-0-77ba57703ace@linaro.org>
Add the gs101-specific reset node, allow it on gs101, and disallow it
on !gs101. Similarly, disallow the generic 'syscon-reboot' on gs101, as
we want the specific one in that case.
Signed-off-by: André Draszik <andre.draszik@linaro.org>
---
.../devicetree/bindings/soc/samsung/exynos-pmu.yaml | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/Documentation/devicetree/bindings/soc/samsung/exynos-pmu.yaml b/Documentation/devicetree/bindings/soc/samsung/exynos-pmu.yaml
index 204da6fe458d2d4bfeee1471ebc5c38247477ae2..8c7362cf3eeab11f6bb13a27eb295d5ee6721b71 100644
--- a/Documentation/devicetree/bindings/soc/samsung/exynos-pmu.yaml
+++ b/Documentation/devicetree/bindings/soc/samsung/exynos-pmu.yaml
@@ -97,6 +97,12 @@ properties:
$ref: /schemas/phy/samsung,dp-video-phy.yaml
unevaluatedProperties: false
+ gs101-reboot:
+ $ref: /schemas/power/reset/google,gs101-reboot.yaml#
+ type: object
+ description:
+ Node for gs101-specific reboot method
+
interrupt-controller:
description:
Some PMUs are capable of behaving as an interrupt controller (mostly
@@ -136,6 +142,21 @@ required:
additionalProperties: false
allOf:
+ - if:
+ properties:
+ compatible:
+ contains:
+ const: google,gs101-pmu
+ then:
+ properties:
+ gs101-reboot: true
+ syscon-reboot: false
+
+ else:
+ properties:
+ gs101-reboot: false
+ syscon-reboot: true
+
- if:
properties:
compatible:
--
2.49.0.472.ge94155a9ec-goog
next prev parent reply other threads:[~2025-03-28 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 15:15 [PATCH v4 0/3] support Linux reboot modes in syscon-reboot on gs101 (Google Pixel) André Draszik
2025-03-28 15:15 ` [PATCH v4 1/3] dt-bindings: power: reset: google,gs101-reboot: add Google GS101 specific reset André Draszik
2025-03-31 7:11 ` Krzysztof Kozlowski
2025-03-28 15:15 ` André Draszik [this message]
2025-03-31 7:15 ` [PATCH v4 2/3] dt-bindings: soc: samsung: exynos-pmu: update reset for gs101 Krzysztof Kozlowski
2025-03-28 15:15 ` [PATCH v4 3/3] power: reset: syscon-reboot: add gs101-specific reset André Draszik
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=20250328-syscon-reboot-reset-mode-v4-2-77ba57703ace@linaro.org \
--to=andre.draszik@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.org \
--cc=sre@kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.com \
/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