From: "Rob Herring (Arm)" <robh@kernel.org>
To: Ciprian Costea <ciprianmarian.costea@oss.nxp.com>
Cc: Enric Balletbo <eballetb@redhat.com>,
devicetree@vger.kernel.org, Will Deacon <will@kernel.org>,
linux-rtc@vger.kernel.org, Christophe Lizzi <clizzi@redhat.com>,
Ghennadi Procopciuc <ghennadi.procopciuc@nxp.com>,
Conor Dooley <conor+dt@kernel.org>,
imx@lists.linux.dev, linux-kernel@vger.kernel.org,
Alberto Ruiz <aruizrui@redhat.com>,
Bogdan-Gabriel Roman <bogdan-gabriel.roman@nxp.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-arm-kernel@lists.infradead.org, NXP S32 Linux <s32@nxp.com>
Subject: Re: [PATCH v6 1/4] dt-bindings: rtc: add schema for NXP S32G2/S32G3 SoCs
Date: Tue, 10 Dec 2024 17:04:33 -0600 [thread overview]
Message-ID: <173387187278.766456.7689697615269440552.robh@kernel.org> (raw)
In-Reply-To: <20241206070955.1503412-2-ciprianmarian.costea@oss.nxp.com>
On Fri, 06 Dec 2024 09:09:52 +0200, Ciprian Costea wrote:
> From: Ciprian Marian Costea <ciprianmarian.costea@oss.nxp.com>
>
> RTC tracks clock time during system suspend and it is used as a wakeup
> source on S32G2/S32G3 architecture.
>
> RTC from S32G2/S32G3 is not battery-powered and it is not kept alive
> during system reset.
>
> Co-developed-by: Bogdan-Gabriel Roman <bogdan-gabriel.roman@nxp.com>
> Signed-off-by: Bogdan-Gabriel Roman <bogdan-gabriel.roman@nxp.com>
> Co-developed-by: Ghennadi Procopciuc <ghennadi.procopciuc@nxp.com>
> Signed-off-by: Ghennadi Procopciuc <ghennadi.procopciuc@nxp.com>
> Signed-off-by: Ciprian Marian Costea <ciprianmarian.costea@oss.nxp.com>
> ---
> .../devicetree/bindings/rtc/nxp,s32g-rtc.yaml | 72 +++++++++++++++++++
> 1 file changed, 72 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/rtc/nxp,s32g-rtc.yaml
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2024-12-10 23:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 7:09 [PATCH v6 0/4] add NXP RTC driver support for S32G2/S32G3 SoCs Ciprian Costea
2024-12-06 7:09 ` [PATCH v6 1/4] dt-bindings: rtc: add schema for NXP " Ciprian Costea
2024-12-10 23:04 ` Rob Herring (Arm) [this message]
2024-12-06 7:09 ` [PATCH v6 2/4] rtc: s32g: add NXP S32G2/S32G3 SoC support Ciprian Costea
2024-12-06 8:04 ` Arnd Bergmann
2024-12-06 12:05 ` Ciprian Marian Costea
2024-12-06 12:41 ` Arnd Bergmann
2024-12-09 17:17 ` Ciprian Marian Costea
2024-12-10 8:22 ` Arnd Bergmann
2024-12-10 23:07 ` Alexandre Belloni
2024-12-10 5:22 ` kernel test robot
2024-12-10 23:25 ` Alexandre Belloni
2025-02-06 10:36 ` Ciprian Marian Costea
2024-12-06 7:09 ` [PATCH v6 3/4] arm64: defconfig: add S32G RTC module support Ciprian Costea
2024-12-06 7:09 ` [PATCH v6 4/4] MAINTAINERS: add NXP S32G RTC driver Ciprian Costea
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=173387187278.766456.7689697615269440552.robh@kernel.org \
--to=robh@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=aruizrui@redhat.com \
--cc=bogdan-gabriel.roman@nxp.com \
--cc=catalin.marinas@arm.com \
--cc=ciprianmarian.costea@oss.nxp.com \
--cc=clizzi@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eballetb@redhat.com \
--cc=ghennadi.procopciuc@nxp.com \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=s32@nxp.com \
--cc=will@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