From: sashiko-bot@kernel.org
To: "Sander Speetjens" <sander.speetjens@gmail.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
linux-rtc@vger.kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: broadcom: Add RTC to Raspberry Pi 5 B
Date: Wed, 09 Sep 2026 14:44:35 +0000 [thread overview]
Message-ID: <20260909144436.585DC1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260909141300.1368790-4-sander.speetjens@gmail.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] The RTC node uses a non-generic node name.
- [Low] Commit message contains multiple obvious spelling mistakes.
--
commit badbff5dbc66bc9afed161f21071dd3b6408304c
Author: Sander Speetjens <sander.speetjens@gmail.com>
arm64: dts: broadcom: Add RTC to Raspberry Pi 5 B
This commit adds a devicetree node for the battery-backed RTC found on the
Raspberry Pi 5's custom DA9091 PMIC, accessed via the firmware mailbox.
> The Raspberry Pi 5 contains a RTC on a custom DA9091 PMIC that is accesed trought the firware mailbox.
> This so we have a battery backed RTC, so the OS does not need network to get the time.
[Severity: Low]
There are a few typos here: "accesed trought the firware" should be "accessed
through the firmware", and "This so we have" should be "This is so we have".
> diff --git a/arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b-base.dtsi b/arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b-base.dtsi
> index b7a6bc34ae1ab..5a82dd585f32b 100644
> --- a/arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b-base.dtsi
> +++ b/arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b-base.dtsi
> @@ -102,6 +102,13 @@ wl_on_reg: wl-on-reg {
> startup-delay-us = <150000>;
> enable-active-high;
> };
> +
> + rpi_rtc: rpi-rtc {
[Severity: Low]
Should this node use a generic name like "rtc" instead of "rpi-rtc"? The
Devicetree specification recommends generic names reflecting the class of the
device rather than the specific model.
> + compatible = "raspberrypi,rpi-rtc";
> + firmware = <&firmware>;
> + status = "okay";
> + trickle-charge-microvolt = <0>;
> + };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260909141300.1368790-1-sander.speetjens@gmail.com?part=3
next prev parent reply other threads:[~2026-09-09 14:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 14:12 [PATCH 0/3] Raspberry Pi 5 RTC driver Sander Speetjens
2026-09-09 14:12 ` [PATCH 1/3] dt-bindings: rtc: Add Raspberry Pi 5 RTC binding Sander Speetjens
2026-09-09 14:23 ` sashiko-bot
2026-09-09 15:15 ` Alexandre Belloni
2026-09-09 15:47 ` Krzysztof Kozlowski
2026-09-09 15:54 ` Krzysztof Kozlowski
2026-09-09 20:38 ` Sander Speetjens
[not found] ` <CAAOJLPHNGgC7B=7ESCifZ1FPcR6V=Hcg-q-aaVg_9M_-d6Fh2A@mail.gmail.com>
2026-09-10 7:08 ` Krzysztof Kozlowski
2026-09-10 8:10 ` Sander Speetjens
2026-09-10 16:33 ` Stefan Wahren
2026-09-09 14:12 ` [PATCH 2/3] rtc: Add Raspberry Pi 5 RTC driver Sander Speetjens
2026-09-09 14:34 ` sashiko-bot
2026-09-09 15:20 ` Alexandre Belloni
2026-09-09 15:22 ` Alexandre Belloni
2026-09-09 15:44 ` Krzysztof Kozlowski
2026-09-09 14:13 ` [PATCH 3/3] arm64: dts: broadcom: Add RTC to Raspberry Pi 5 B Sander Speetjens
2026-09-09 14:44 ` sashiko-bot [this message]
2026-09-09 15:47 ` 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=20260909144436.585DC1F00A3A@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