From: pjh456 <pengjunhao409@gmail.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v4] dt-bindings: rtc: haoyu,hym8563: document vdd-supply
Date: Fri, 20 Nov 2026 19:35:01 +0800 [thread overview]
Message-ID: <20261120113502.563894-1-pengjunhao409@gmail.com> (raw)
The HYM8563 is supplied through its VDD pin. Add an optional
vdd-supply property so a board can describe the regulator connected
to it.
The property is optional because some boards connect VDD to an
always-on rail. Describing the supply also lets fw_devlink order the
RTC probe after its regulator.
Signed-off-by: pjh456 <pengjunhao409@gmail.com>
---
v4: rewrite the commit message, move the AI disclosure below --- and
drop the version links. No code changes.
v3: use the generic "vdd-supply: true" form and show the supply in the
example; reword the rationale around the hardware instead of the
fw_devlink ordering; replace the non-standard "Assisted-by:"
trailers with a disclosure paragraph in the commit message.
v2: rename vcc-supply to vdd-supply, matching the datasheet pin name.
The patch was tested on the Purple Pi OH: cold boot, same kernel Image,
only the DTB changed. With vdd-supply, 3/3 boots registered hym8563
as rtc0 at ~0.6 s. Without it, 2/2 boots failed with -110 at ~1.37 s
because the RTC probed before the i2c3 pull-up rail (vccio_acodec)
reached 3.3 V at ~1.60 s.
AI assistance: I used the HYM8563 datasheet and the board schematic as
inputs, and drafted this change with help from Qwen3.8 Flash Next and
DeepSeek V4.1 Flash through the OpenCode coding agent; Gemini 4
Hydrogen was used to cross-check the schematic in Google AI Studio.
I reviewed the result, ran dt_binding_check, and tested it on the board.
Documentation/devicetree/bindings/rtc/haoyu,hym8563.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/rtc/haoyu,hym8563.yaml b/Documentation/devicetree/bindings/rtc/haoyu,hym8563.yaml
index 0b9f39ef0edc..ce9712e2c406 100644
--- a/Documentation/devicetree/bindings/rtc/haoyu,hym8563.yaml
+++ b/Documentation/devicetree/bindings/rtc/haoyu,hym8563.yaml
@@ -29,6 +29,8 @@ properties:
wakeup-source:
description: Enables wake up of host system on alarm.
+ vdd-supply: true
+
allOf:
- $ref: rtc.yaml
@@ -52,5 +54,6 @@ examples:
reg = <0x51>;
interrupts = <13 IRQ_TYPE_EDGE_FALLING>;
#clock-cells = <0>;
+ vdd-supply = <&rtc_vdd>;
};
};
base-commit: 7e1392a42ea288d70a266f6553fe06f57f8647ea
--
2.56.1
next reply other threads:[~2026-11-20 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 11:35 pjh456 [this message]
2026-11-20 11:44 ` [PATCH v4] dt-bindings: rtc: haoyu,hym8563: document vdd-supply sashiko-bot
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=20261120113502.563894-1-pengjunhao409@gmail.com \
--to=pengjunhao409@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.