From: sashiko-bot@kernel.org
To: "Sander Speetjens" <sander.speetjens@gmail.com>
Cc: linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH v12 3/3] rtc: Add Raspberry Pi 5 RTC driver
Date: Sun, 18 Oct 2026 14:45:41 +0000 [thread overview]
Message-ID: <sashiko-outbox-176212@kernel.org> (raw)
In-Reply-To: <20261018143712.1040152-4-sander.speetjens@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] rtc: Kconfig RTC_DRV_RPI depends on ARCH_BRCMSTB instead of ARCH_BCM2835
--
commit 764db262bbaebd42035bc0933220419e0e4cbc7d
Author: Sander Speetjens <sander.speetjens@gmail.com>
rtc: Add Raspberry Pi 5 RTC driver
This commit adds the Raspberry Pi 5 RTC driver, which accesses the custom
DA9091 RTC through the Raspberry Pi firmware mailbox, and registers the
raspberrypi-rtc platform device from drivers/firmware/raspberrypi.c on
brcm,bcm2712 machines.
> diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
> index 05b9233b94189..6adaf425a76bc 100644
> --- a/drivers/rtc/Kconfig
> +++ b/drivers/rtc/Kconfig
> @@ -1999,6 +1999,18 @@ config RTC_DRV_R7301
> This driver can also be built as a module. If so, the module
> will be called rtc-r7301.
>
> +config RTC_DRV_RPI
> + tristate "Raspberry Pi RTC"
> + depends on RASPBERRYPI_FIRMWARE || (COMPILE_TEST && !RASPBERRYPI_FIRMWARE)
> + depends on ARCH_BRCMSTB || COMPILE_TEST
> + default ARCH_BRCMSTB
[Severity: Medium]
Should RTC_DRV_RPI depend on and default to ARCH_BCM2835 instead of
ARCH_BRCMSTB (or rely on the RASPBERRYPI_FIRMWARE dependency)?
In drivers/firmware/Kconfig, RASPBERRYPI_FIRMWARE is gated on ARCH_BCM2835:
config RASPBERRYPI_FIRMWARE
tristate "Raspberry Pi Firmware Driver"
depends on ARCH_BCM2835 || COMPILE_TEST
depends on ARM || ARM64
depends on MAILBOX
default ARCH_BCM2835
When COMPILE_TEST=n, a configuration with ARCH_BCM2835=y,
RASPBERRYPI_FIRMWARE=y, and ARCH_BRCMSTB=n will register the
raspberrypi-rtc platform device in rpi_register_rtc_driver(), but
RTC_DRV_RPI cannot be enabled. Conversely, with ARCH_BRCMSTB=y and
ARCH_BCM2835=n, RASPBERRYPI_FIRMWARE cannot be enabled, so RTC_DRV_RPI's
first dependency is not satisfied.
> + help
> + If you say yes here you get support for the RTC found on
> + Raspberry Pi 5th gen devices.
> +
> + This driver can also be built as a module. If so, the module
> + will be called rtc-raspberrypi.
> +
> config RTC_DRV_STM32
> tristate "STM32 RTC"
> select REGMAP_MMIO
[ ... ]
>
>
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261018143712.1040152-1-sander.speetjens@gmail.com?part=3
prev parent reply other threads:[~2026-10-18 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 14:37 [PATCH v12 0/3] Raspberry Pi 5 RTC driver Sander Speetjens
2026-10-18 14:37 ` [PATCH v12 1/3] dt-bindings: rtc: Add missing type to trickle-voltage-millivolt Sander Speetjens
2026-10-18 14:37 ` [PATCH v12 2/3] dt-bindings: rtc: Add property for Raspberry Pi 5 RTC Sander Speetjens
2026-10-18 14:37 ` [PATCH v12 3/3] rtc: Add Raspberry Pi 5 RTC driver Sander Speetjens
2026-10-18 14:45 ` sashiko-bot [this message]
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-176212@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