From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: "Lad Prabhakar" <prabhakar.csengg@gmail.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-rtc@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Rob Herring <robh@kernel.org>
Subject: [PATCH v2 0/4] rtc: rzn1: cleanups, R-Car Gen5 enablement
Date: Wed, 16 Sep 2026 12:25:15 +0200 [thread overview]
Message-ID: <20260916102520.24288-1-wsa+renesas@sang-engineering.com> (raw)
This series adds RTC support for the Renesas R-Car Gen5 SoCs.
Changes since v1:
* don't support non-interrupt mode in general, but implement it only for
X5H while still requiring irqs for all other SoCs
* add tags to cleanup patches
Thanks for all the reviews of v1!
These patches have been tested on the original RZ/N1D board and the new
X5H Ironhide board. 'rtctest' passed on both SoCs. On X5H, some tests
are skipped, of course, because no alarms are supported.
'dt_binding_check' and 'dtbs_check' did not find any issues, for both,
RZ/N1D and R-Car X5H. I also verified for both that it rightfully
complains when irqs are different from what is expected.
A branch can be found here:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/x5h/rtc-experimental
Looking forward to comments.
Wolfram Sang (4):
dt-bindings: rtc: rzn1: drop unneeded 'start-year' from example
dt-bindings: rtc: rzn1: add SoC names next to their IDs
dt-bindings: rtc: rzn1: add R-Car Gen5 support
rtc: rzn1: add R-Car Gen5 support
.../bindings/rtc/renesas,rzn1-rtc.yaml | 33 +++++++++---
drivers/rtc/rtc-rzn1.c | 54 ++++++++++++-------
2 files changed, 61 insertions(+), 26 deletions(-)
--
2.53.0
next reply other threads:[~2026-09-16 10:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 10:25 Wolfram Sang [this message]
2026-09-16 10:25 ` [PATCH v2 1/4] dt-bindings: rtc: rzn1: drop unneeded 'start-year' from example Wolfram Sang
2026-09-16 10:27 ` sashiko-bot
2026-09-16 13:23 ` Geert Uytterhoeven
2026-09-16 10:25 ` [PATCH v2 2/4] dt-bindings: rtc: rzn1: add SoC names next to their IDs Wolfram Sang
2026-09-16 10:27 ` sashiko-bot
2026-09-16 13:24 ` Geert Uytterhoeven
2026-09-16 10:25 ` [PATCH v2 3/4] dt-bindings: rtc: rzn1: add R-Car Gen5 support Wolfram Sang
2026-09-16 10:31 ` sashiko-bot
2026-09-16 12:13 ` Lad, Prabhakar
2026-09-16 13:25 ` Geert Uytterhoeven
2026-09-24 21:51 ` Rob Herring (Arm)
2026-09-16 10:25 ` [PATCH v2 4/4] " Wolfram Sang
2026-09-16 10:31 ` sashiko-bot
2026-09-16 12:19 ` Lad, Prabhakar
2026-09-16 13:33 ` Geert Uytterhoeven
2026-09-16 21:36 ` Wolfram Sang
2026-09-16 11:45 ` [PATCH v2 0/4] rtc: rzn1: cleanups, R-Car Gen5 enablement Wolfram Sang
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=20260916102520.24288-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=prabhakar.csengg@gmail.com \
--cc=robh@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