From: Frank Li <Frank.li@nxp.com>
To: Ciprian Costea <ciprianmarian.costea@oss.nxp.com>
Cc: Shawn Guo <shawnguo@kernel.org>,
linux-kernel@vger.kernel.org,
Christophe Lizzi <clizzi@redhat.com>,
Alberto Ruiz <aruizrui@redhat.com>,
Enric Balletbo <eballetb@redhat.com>,
Eric Chanudet <echanude@redhat.com>,
imx@lists.linux.dev
Subject: Re: [PATCH] arm64: dts: s32g: add RTC node
Date: Wed, 28 May 2025 11:41:14 -0400 [thread overview]
Message-ID: <aDcumpWLhNh98WVR@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20250526162954.2467894-1-ciprianmarian.costea@oss.nxp.com>
On Mon, May 26, 2025 at 07:29:53PM +0300, Ciprian Costea wrote:
> From: Ciprian Marian Costea <ciprianmarian.costea@oss.nxp.com>
>
> The RTC module on S32G2/S32G3 based SoCs is used as a wakeup source from
> system suspend.
>
> Signed-off-by: Ciprian Marian Costea <ciprianmarian.costea@oss.nxp.com>
Reviewed-by: Frank Li <Frank.Li@nxp.com>
> ---
> arch/arm64/boot/dts/freescale/s32g2.dtsi | 8 ++++++++
> arch/arm64/boot/dts/freescale/s32g3.dtsi | 9 +++++++++
> 2 files changed, 17 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/s32g2.dtsi b/arch/arm64/boot/dts/freescale/s32g2.dtsi
> index fa054bfe7d5c..39d12422e3f3 100644
> --- a/arch/arm64/boot/dts/freescale/s32g2.dtsi
> +++ b/arch/arm64/boot/dts/freescale/s32g2.dtsi
> @@ -114,6 +114,14 @@ soc@0 {
> #size-cells = <1>;
> ranges = <0 0 0 0x80000000>;
>
> + rtc0: rtc@40060000 {
> + compatible = "nxp,s32g2-rtc";
> + reg = <0x40060000 0x1000>;
> + interrupts = <GIC_SPI 121 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&clks 54>, <&clks 55>;
> + clock-names = "ipg", "source0";
> + };
> +
> pinctrl: pinctrl@4009c240 {
> compatible = "nxp,s32g2-siul2-pinctrl";
> /* MSCR0-MSCR101 registers on siul2_0 */
> diff --git a/arch/arm64/boot/dts/freescale/s32g3.dtsi b/arch/arm64/boot/dts/freescale/s32g3.dtsi
> index b4226a9143c8..e71b80e048dc 100644
> --- a/arch/arm64/boot/dts/freescale/s32g3.dtsi
> +++ b/arch/arm64/boot/dts/freescale/s32g3.dtsi
> @@ -171,6 +171,15 @@ soc@0 {
> #size-cells = <1>;
> ranges = <0 0 0 0x80000000>;
>
> + rtc0: rtc@40060000 {
> + compatible = "nxp,s32g3-rtc",
> + "nxp,s32g2-rtc";
> + reg = <0x40060000 0x1000>;
> + interrupts = <GIC_SPI 121 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&clks 54>, <&clks 55>;
> + clock-names = "ipg", "source0";
> + };
> +
> pinctrl: pinctrl@4009c240 {
> compatible = "nxp,s32g2-siul2-pinctrl";
> /* MSCR0-MSCR101 registers on siul2_0 */
> --
> 2.45.2
>
next prev parent reply other threads:[~2025-05-28 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 16:29 Ciprian Costea
2025-05-26 16:29 ` [PATCH] MAINTAINERS: add NXP S32G RTC driver Ciprian Costea
2025-05-26 16:31 ` Ciprian Marian Costea
2025-05-26 16:32 ` [PATCH] arm64: dts: s32g: add RTC node Ciprian Marian Costea
2025-05-28 15:41 ` Frank Li [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-26 16:21 Ciprian Costea
2025-05-26 18:20 ` Matthias Brugger
2025-06-19 7:48 ` Ciprian Marian Costea
2025-06-19 7:55 ` Shawn Guo
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=aDcumpWLhNh98WVR@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=aruizrui@redhat.com \
--cc=ciprianmarian.costea@oss.nxp.com \
--cc=clizzi@redhat.com \
--cc=eballetb@redhat.com \
--cc=echanude@redhat.com \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnguo@kernel.org \
/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®