From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
linux-rtc@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
devicetree@vger.kernel.org,
Gareth Williams <gareth.williams.jx@renesas.com>,
Milan Stevanovic <milan.stevanovic@se.com>,
Jimmy Lalande <jimmy.lalande@se.com>,
Pascal Eberhard <pascal.eberhard@se.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Herve Codina <herve.codina@bootlin.com>,
Clement Leger <clement.leger@bootlin.com>
Subject: [PATCH v3 0/6] RZN1 RTC support
Date: Fri, 29 Apr 2022 12:45:56 +0200 [thread overview]
Message-ID: <20220429104602.368055-1-miquel.raynal@bootlin.com> (raw)
Hello,
This small series adds support for the RZN1 RTC.
Despite its limitations, I found useful to at least have alarm and
offset support.
The RTC hclk fix has been merged in the renesas-clk-for-v5.19 branch so
I dropped it from the series.
Cheers,
Miquèl
Changes in v3:
* Collected tags.
* s/soc:/clk:/ in the clock commit title.
* Dropped the RTC hclk fix which has already been applied.
* Added the power-domain properties both in the bindings and in the DT.
* Used runtime PM to enable the clock instead of using the clk API
directly.
Changes in v2:
* Fixed the error path in the clk driver, where I missed to release a
spin_lock.
* Collected tags.
* Moved the rtc subnode in the dt to keep the nodes ordered by unit
address.
* Dropped the useless "oneOf" statement in the bindings (compatible
property).
* Dropped the start-year property in the bindings (already defined).
* Avoided rollover calculations that could be more easily handled (and
reviewed) with a time64_t conversion.
* Returned ERANGE instead of EOPNOTSUPP when the alarm date is not
valid.
* Cleared RTC_FEATURE_UPDATE_INTERRUPT to avoid warning from the tools.
* Dropped the sysctl patch adding the reset helper, instead fulfilled
the description of the RTC clock so that when requesting this clock to
be enabled, the idle bit is released.
* Avoided rollover calculations that could be more easily handled
(and reviewed) with a time64_t conversion.
* Fixed the max_range value, after a rtc-range test and looking at other
implementations.
Michel Pollet (1):
rtc: rzn1: Add new RTC driver
Miquel Raynal (5):
dt-bindings: rtc: rzn1: Describe the RZN1 RTC
rtc: rzn1: Add alarm support
rtc: rzn1: Add oscillator offset support
MAINTAINERS: Add myself as maintainer of the RZN1 RTC driver
ARM: dts: r9a06g032: Describe the RTC
.../bindings/rtc/renesas,rzn1-rtc.yaml | 70 +++
MAINTAINERS | 8 +
arch/arm/boot/dts/r9a06g032.dtsi | 13 +
drivers/rtc/Kconfig | 7 +
drivers/rtc/Makefile | 1 +
drivers/rtc/rtc-rzn1.c | 423 ++++++++++++++++++
6 files changed, 522 insertions(+)
create mode 100644 Documentation/devicetree/bindings/rtc/renesas,rzn1-rtc.yaml
create mode 100644 drivers/rtc/rtc-rzn1.c
--
2.27.0
next reply other threads:[~2022-04-29 10:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 10:45 Miquel Raynal [this message]
2022-04-29 10:45 ` [PATCH v3 1/6] dt-bindings: rtc: rzn1: Describe the RZN1 RTC Miquel Raynal
2022-04-29 10:45 ` [PATCH v3 2/6] rtc: rzn1: Add new RTC driver Miquel Raynal
2022-05-02 14:41 ` Geert Uytterhoeven
2022-05-09 14:59 ` Miquel Raynal
2022-04-29 10:45 ` [PATCH v3 3/6] rtc: rzn1: Add alarm support Miquel Raynal
2022-05-02 14:45 ` Geert Uytterhoeven
2022-04-29 10:46 ` [PATCH v3 4/6] rtc: rzn1: Add oscillator offset support Miquel Raynal
2022-04-29 10:46 ` [PATCH v3 5/6] MAINTAINERS: Add myself as maintainer of the RZN1 RTC driver Miquel Raynal
2022-04-29 10:46 ` [PATCH v3 6/6] ARM: dts: r9a06g032: Describe the RTC Miquel Raynal
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=20220429104602.368055-1-miquel.raynal@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=clement.leger@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=gareth.williams.jx@renesas.com \
--cc=geert+renesas@glider.be \
--cc=herve.codina@bootlin.com \
--cc=jimmy.lalande@se.com \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=milan.stevanovic@se.com \
--cc=pascal.eberhard@se.com \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.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