From: Heiko Schocher <hs@nabladev.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: linux-rtc@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, Heiko Schocher <hs@nabladev.com>
Subject: [PATCH v1 0/3] rtc: rs5c372: add Ricoh R2223x support
Date: Mon, 24 Aug 2026 13:04:23 +0200 [thread overview]
Message-ID: <20260824110452.4038870-1-hs@nabladev.com> (raw)
The Ricoh R2223x is an I2C RTC from the same family as the r2025sd and
r2221tl which the rtc-rs5c372 already supports. It shares the R2x2x
control register layout, so only the new type must be added to the driver.
The ricoh R2223x drives a clock output and offers an eco mode that
lowers its current consumption while running from the backup supply.
The trivial-rtc binding does not cover this, so give the device its
own binding in patch 1. Patch 2 adds the R2223x to the rs5c372 rtc
driver, and patch 3 implements the eco-mode enable setting.
Heiko Schocher (3):
dt-bindings: rtc: add ricoh,r2223x binding
rtc: rs5c372: add support for Ricoh R2223x
rtc: rs5c372: support eco mode on R2223x
.../devicetree/bindings/rtc/ricoh,r2223x.yaml | 58 +++++++++++++++++++
drivers/rtc/rtc-rs5c372.c | 41 ++++++++++++-
2 files changed, 98 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/rtc/ricoh,r2223x.yaml
---
base-commit: 2709dd5ae32f0828f386327c76bba9f39f63a1c6
--
2.55.0
next reply other threads:[~2026-08-24 11:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 11:04 Heiko Schocher [this message]
2026-08-24 11:04 ` [PATCH v1 1/3] dt-bindings: rtc: add ricoh,r2223x binding Heiko Schocher
2026-08-24 11:08 ` sashiko-bot
2026-08-24 16:26 ` Conor Dooley
2026-08-24 11:04 ` [PATCH v1 2/3] rtc: rs5c372: add support for Ricoh R2223x Heiko Schocher
2026-08-24 11:14 ` sashiko-bot
2026-08-24 11:04 ` [PATCH v1 3/3] rtc: rs5c372: support eco mode on R2223x Heiko Schocher
2026-08-24 11:15 ` sashiko-bot
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=20260824110452.4038870-1-hs@nabladev.com \
--to=hs@nabladev.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--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