From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: 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: [RFC PATCH 0/4] rtc: rzn1: support XTAL clk and SCMP method
Date: Thu, 13 Mar 2025 11:25:41 +0100 [thread overview]
Message-ID: <20250313102546.27335-1-wsa+renesas@sang-engineering.com> (raw)
So far, the code and the binding for the RZ/N1D RTC assumed an input
clock of 32768Hz, so it was not explicitly described. It makes sense to
do this, though. For one reason, clocks with other frequencies might be
used which this RTC supports via the SCMP counting method. Also, the
upcoming R-Car Gen5 have only the SCMP method described, so we need to
use it there.
This series is for collecting comments about the approach. I am aware
that the DTS changes no to go in separately from the code changes. And
the last patch will be updated and resent once I have tested these
patches on hardware. That might take a while but I'd like the
preparational patches to go in earlier. They are benefitial for N1D,
after all.
The series has been tested on a Renesas RZ/N1D board with hacked
devicetree values.
Looking forward to comments.
Wolfram Sang (4):
dt-bindings: rtc: rzn1: add optional second clock
ARM: dts: renesas: r9a06g032: add second clock input to RTC
rtc: rzn1: support input frequencies other than 32768Hz
WIP rtc: rzn1: add driver support for R-Car Gen5
.../bindings/rtc/renesas,rzn1-rtc.yaml | 8 ++-
.../dts/renesas/r9a06g032-rzn1d400-db.dts | 4 ++
arch/arm/boot/dts/renesas/r9a06g032.dtsi | 4 +-
drivers/rtc/rtc-rzn1.c | 67 ++++++++++++++++---
4 files changed, 70 insertions(+), 13 deletions(-)
--
2.47.2
next reply other threads:[~2025-03-13 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 10:25 Wolfram Sang [this message]
2025-03-13 10:25 ` [RFC PATCH 1/4] dt-bindings: rtc: rzn1: add optional second clock Wolfram Sang
2025-03-14 8:41 ` Krzysztof Kozlowski
2025-03-14 8:54 ` Wolfram Sang
2025-03-13 10:25 ` [RFC PATCH 2/4] ARM: dts: renesas: r9a06g032: add second clock input to RTC Wolfram Sang
2025-04-10 15:32 ` Geert Uytterhoeven
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=20250313102546.27335-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=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;
as well as URLs for NNTP newsgroup(s).