From: sashiko-bot@kernel.org
To: "Mike Hsieh" <mike.quanta.115@gmail.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH] ARM: dts: aspeed: clemente: Remove nct3018y rtc node
Date: Mon, 31 Aug 2026 16:31:45 +0000 [thread overview]
Message-ID: <20260831163145.A11E11F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260831-clemente-remove-rtc-v1-1-84fc5787a6bb@quantatw.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Removing the RTC node to rely on userspace instantiation violates DT principles and breaks early boot time synchronization.
--
commit d669dbe540f28ffaac22aefa950b8d7090cfaf67
Author: Mike Hsieh <mike.quanta.115@gmail.com>
ARM: dts: aspeed: clemente: Remove nct3018y rtc node
This commit removes the statically defined nct3018y RTC node from the
Clemente device tree because a second-source RTC chip might be present. It
defers the initialization of the RTC driver to userspace or an early-init
script.
> diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-clemente.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-clemente.dts
> index 820d39a929746..51e90a4fba0ea 100644
> --- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-clemente.dts
> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-clemente.dts
> @@ -958,11 +958,6 @@ io_expander3: gpio@21 {
> "",
> "";
> };
> -
> - rtc@6f {
> - compatible = "nuvoton,nct3018y";
> - reg = <0x6f>;
> - };
[Severity: Medium]
Does removing the hardware description of the RTC and deferring its
initialization to userspace break early boot time synchronization?
Removing the RTC from the Device Tree prevents the kernel from probing the
RTC driver during early boot. This breaks CONFIG_RTC_HCTOSYS (which runs as
a late_initcall before userspace execution), causing the kernel to boot
with a default epoch time. This can corrupt timestamps in early kernel logs
and trigger false-positive failures during early root filesystem mount
checks.
Additionally, using userspace scripts to instantiate permanently attached
on-board I2C devices via sysfs (new_device) is a well-known architectural
anti-pattern. Is it possible to have the bootloader fix up the DT for
second-source components before passing it to the kernel instead?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260831-clemente-remove-rtc-v1-1-84fc5787a6bb@quantatw.com?part=1
prev parent reply other threads:[~2026-08-31 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 13:47 [PATCH] ARM: dts: aspeed: clemente: Remove nct3018y rtc node Mike Hsieh
2026-08-31 16:31 ` 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=20260831163145.A11E11F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=mike.quanta.115@gmail.com \
--cc=robh@kernel.org \
--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