From: sashiko-bot@kernel.org
To: "Sander Speetjens" <sander.speetjens@gmail.com>
Cc: "Alexandre Belloni" <alexandre.belloni@bootlin.com>,
conor+dt@kernel.org, linux-rtc@vger.kernel.org,
devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: rtc: Add property for Raspberry Pi 5 RTC
Date: Thu, 17 Sep 2026 12:30:21 +0000 [thread overview]
Message-ID: <20260917123022.150D81F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260917122144.703221-2-sander.speetjens@gmail.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] dt-bindings: invalid $ref to non-existent property charging-voltage-millivolt
- [Medium] dt-bindings: undeclared property trickle-charge-millivolt in example
--
commit 387f082415e97ddf81bc4779459443584085928f
Author: Sander Speetjens <sander.speetjens@gmail.com>
dt-bindings: rtc: Add property for Raspberry Pi 5 RTC
This commit adds a new property to configure the charging voltage for the
Raspberry Pi 5 RTC within the bcm2835-firmware binding.
> diff --git a/Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.yaml b/Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.yaml
> index 983ea80eaec97..1a0432510beeb 100644
> --- a/Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.yaml
> +++ b/Documentation/devicetree/bindings/arm/bcm/raspberrypi,bcm2835-firmware.yaml
> @@ -133,6 +133,11 @@ properties:
> required:
> - compatible
>
> + charging-voltage-millivolt:
> + $ref: /schemas/rtc/rtc.yaml#/properties/charging-voltage-millivolt
[Severity: Medium]
Does the standard rtc.yaml define charging-voltage-millivolt?
Looking at the standard RTC binding (rtc.yaml), it does not define this
property. The correct standard name appears to be trickle-voltage-millivolt.
This invalid schema reference will cause make dt_binding_check to fail to
resolve the path and import constraints, breaking schema validation.
> + minimum: 1300
> + maximum: 5000
> +
> required:
> - compatible
[ ... ]
> @@ -171,5 +176,7 @@ examples:
> touchscreen-size-x = <800>;
> touchscreen-size-y = <480>;
> };
> +
> + trickle-charge-millivolt = <3300>;
[Severity: Medium]
Should this example property name match the one declared above?
The patch defines charging-voltage-millivolt in the properties block, but
the example uses trickle-charge-millivolt. Because additional properties are
restricted by the schema rules, the use of an undeclared property in the
example will trigger a strict validation failure during make dt_binding_check.
> };
> ...
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260917122144.703221-1-sander.speetjens@gmail.com?part=1
next prev parent reply other threads:[~2026-09-17 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 12:21 [PATCH v2 0/2] Raspberry Pi 5 RTC driver Sander Speetjens
2026-09-17 12:21 ` [PATCH v2 1/2] dt-bindings: rtc: Add property for Raspberry Pi 5 RTC Sander Speetjens
2026-09-17 12:30 ` sashiko-bot [this message]
2026-09-17 12:21 ` [PATCH v2 2/2] rtc: Add Raspberry Pi 5 RTC driver Sander Speetjens
2026-09-17 12:40 ` 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=20260917123022.150D81F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sander.speetjens@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