On Tue, Sep 29, 2026 at 02:28:19PM +0400, Alexey Charkov wrote:
Whatever program that acts on a reboot mode runs before a full OS, so it
may lack the capability to enable the regulators it depends on, and a
reset that preserves the mode register generally leaves the regulators as
the previously running system left them.
Allow a reboot mode node to name such supplies, so that they can be
turned on while the mode is being requested.
Tested-by: Shawn Lin <shawn.lin@rock-chips.com>
Again fake tag.
quoted hunk ↗ jump to hunk
Signed-off-by: Alexey Charkov <redacted>
---
.../devicetree/bindings/power/reset/syscon-reboot-mode.yaml | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/Documentation/devicetree/bindings/power/reset/syscon-reboot-mode.yaml b/Documentation/devicetree/bindings/power/reset/syscon-reboot-mode.yaml
index 79ffc78b23ea..5ed70c87269e 100644
--- a/Documentation/devicetree/bindings/power/reset/syscon-reboot-mode.yaml
+++ b/Documentation/devicetree/bindings/power/reset/syscon-reboot-mode.yaml
@@ -36,6 +36,14 @@ patternProperties:
"^mode-.*$":
maxItems: 1
+ "^[a-z0-9]+(-[a-z0-9]+)*-supply$":
+ description:
+ Supply that has to be powered for whatever program acts on the mode.
+ That could be a boot ROM with no access to regulators, and a warm reset
+ leaves them as the previously running system left them and not necessarily
+ what their expected out-of-reboot state is. Any supply described here is
+ enabled when a mode is requested, and stays enabled.
This looks like workaround for missing supply handling in actual
consumers. Fix your devices instead.
Best regards,
Krzysztof