Linux RTC
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: pjh456 <pengjunhao409@gmail.com>
Cc: linux-rtc@vger.kernel.org,
	"Alexandre Belloni" <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH v3] dt-bindings: rtc: haoyu,hym8563: document vdd-supply
Date: Thu, 19 Nov 2026 12:54:26 +0000	[thread overview]
Message-ID: <sashiko-outbox-223121@kernel.org> (raw)
In-Reply-To: <20261119125125.75912-1-pengjunhao409@gmail.com>

> 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>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261119125125.75912-1-pengjunhao409@gmail.com?part=1


  reply	other threads:[~2026-11-19 12:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19 12:51 [PATCH v3] dt-bindings: rtc: haoyu,hym8563: document vdd-supply pjh456
2026-11-19 12:54 ` sashiko-bot [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=sashiko-outbox-223121@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=linux-rtc@vger.kernel.org \
    --cc=pengjunhao409@gmail.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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