From: Sander Speetjens <sander.speetjens@gmail.com>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Jonathan Bell <jonathan@raspberrypi.com>,
linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, pbrobinson@gmail.com,
Dom Cobley <popcornmix@gmail.com>
Subject: Re: [PATCH v8 2/2] rtc: Add Raspberry Pi 5 RTC driver
Date: Wed, 30 Sep 2026 21:07:00 +0200 [thread overview]
Message-ID: <bd02376e-f42a-4251-8e7d-7c4e7579a845@gmail.com> (raw)
In-Reply-To: <550045ab-fe74-4445-8f6c-4a031f5b436b@gmx.net>
>>>> +MODULE_ALIAS("platform:raspberrypi-rtc");
>>> Is this really necessary for module autoloading?
>> I'm not sure, it was used in the previous versions when using the
>> platform device register on the register_clk driver before it had a
>> custom dt node.
> You can test by removing the line and compile it as a module. In case
> the RTC driver is still automatically loaded, we can drop it.
There is no DT node for the RTC. The firmware driver registers us as a
platform device at runtime (we deliberately avoid a child node per DT
maintainer guidance). Therefore the platform alias is still needed for
module auto-loading.
prev parent reply other threads:[~2026-09-30 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 9:52 [PATCH v8 0/2] Raspberry Pi 5 RTC driver Sander Speetjens
2026-09-30 9:52 ` [PATCH v8 1/2] dt-bindings: rtc: Add property for Raspberry Pi 5 RTC Sander Speetjens
2026-09-30 9:52 ` [PATCH v8 2/2] rtc: Add Raspberry Pi 5 RTC driver Sander Speetjens
2026-09-30 16:50 ` Stefan Wahren
2026-09-30 17:29 ` Sander Speetjens
2026-09-30 18:44 ` Stefan Wahren
2026-09-30 19:07 ` Sander Speetjens [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=bd02376e-f42a-4251-8e7d-7c4e7579a845@gmail.com \
--to=sander.speetjens@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=jonathan@raspberrypi.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=pbrobinson@gmail.com \
--cc=popcornmix@gmail.com \
--cc=robh@kernel.org \
--cc=wahrenst@gmx.net \
/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