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 v3] dt-bindings: rtc: haoyu,hym8563: document vdd-supply
Date: Thu, 19 Nov 2026 20:51:24 +0800 [thread overview]
Message-ID: <20261119125125.75912-1-pengjunhao409@gmail.com> (raw)
VDD is the HYM8563's main supply pin. Describe it so boards can
express the regulator feeding the RTC; the property is optional
because many boards hardwire VDD to an always-on rail. A side effect
of describing it is that fw_devlink orders the RTC probe after its
supply. The Purple Pi OH board DTS (posted separately) relies on
that ordering.
AI assistance: the supply description was cross-checked against the
vendor schematic with Gemini 4 Hydrogen (Google AI Studio); the binding
change and this changelog were drafted with assistance from the
Qwen3.8 Flash Next and DeepSeek V4.1 Flash language models, driven
through the OpenCode coding agent, using the HYM8563 datasheet as
input; the submitter reviewed every line, validated the result with
dt_binding_check and on the affected board, and takes full
responsibility for it.
Link: https://lore.kernel.org/all/tencent_B11DE1495C3C54CE186ED508E2CE5CE41106@qq.com/
Link: https://lore.kernel.org/all/tencent_9B1CC4BF39DFA325C2B5384EA8B0319BAA07@qq.com/
Signed-off-by: pjh456 <pengjunhao409@gmail.com>
---
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
(Sashiko review).
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-19 12:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 12:51 pjh456 [this message]
2026-11-19 13:18 ` Krzysztof Kozlowski
2026-11-19 13:20 ` Krzysztof Kozlowski
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=20261119125125.75912-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®