From: Andrei Botila <andrei.botila@oss.nxp.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Conor Dooley <conor+dt@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Ghennadi Procopciuc <ghennadi.procopciuc@oss.nxp.com>,
NXP S32 Linux Team <s32@nxp.com>,
Chester Lin <chester62515@gmail.com>,
Matthias Brugger <mbrugger@suse.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: s32g: force S32G RTC as rtc0
Date: Tue, 10 Mar 2026 15:49:54 +0200 [thread overview]
Message-ID: <67e082c5-2b34-4960-8fd1-6cd007e0584c@oss.nxp.com> (raw)
In-Reply-To: <CAOMZO5BVtRHW1+qtMEH9akO7ULS3LppzGXMB2_M-JJVwjbv1oQ@mail.gmail.com>
On 3/10/2026 3:14 PM, Fabio Estevam wrote:
> On Tue, Mar 10, 2026 at 9:50 AM Andrei Botila <andrei.botila@oss.nxp.com> wrote:
>>
>> S32G RTC is probed after the RTC on RDB (PCA85073A) so the S32G RTC
>> ends up on /dev/rtc1. This causes the suspend/resume or hwclock to use
>> the wrong RTC since it takes by default rtc0.
>> Force the S32G RTC to be assigned rtc0.
>
> We usually prefer to use the I2C RTC as rtc0 because it is battery-backed.
>
> What's the exact problem with using the I2C RTC as rtc0?
>
> Is the S32G RTC battery-backed?
Hello,
S32G RTC is not battery-backed.
Regarding the I2C RTC(PCA85073A) commands like hwclock or rtcwake use by
default /dev/rtc, /dev/rtc0 so they will try to use PCA and fail.
Also from what I could find online PCA85073A is also not battery-backed.
Thank you,
Andrei
next prev parent reply other threads:[~2026-03-10 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 12:49 Andrei Botila
2026-03-10 13:14 ` Fabio Estevam
2026-03-10 13:49 ` Andrei Botila [this message]
2026-03-10 14:02 ` Fabio Estevam
2026-03-10 15:21 ` Andrei Botila
2026-03-10 16:03 ` Fabio Estevam
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=67e082c5-2b34-4960-8fd1-6cd007e0584c@oss.nxp.com \
--to=andrei.botila@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=chester62515@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=ghennadi.procopciuc@oss.nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbrugger@suse.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=s32@nxp.com \
/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
all inboxes | Powered by JetHome®