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 1/3] dt-bindings: rtc: add ricoh,r2223x binding
Date: Mon, 24 Aug 2026 13:04:24 +0200 [thread overview]
Message-ID: <20260824110452.4038870-2-hs@nabladev.com> (raw)
In-Reply-To: <20260824110452.4038870-1-hs@nabladev.com>
The Ricoh R2223x is an I2C RTC of the same family as the r2025sd and
r2221tl which the rtc-rs5c372 already supports. It drives a clock output
and can be put into an eco mode that lowers its current consumption from
the backup supply, so it needs #clock-cells and a property for the eco
mode.
The trivial-rtc binding does not cover this, so give the device its
own binding.
Signed-off-by: Heiko Schocher <hs@nabladev.com>
---
.../devicetree/bindings/rtc/ricoh,r2223x.yaml | 58 +++++++++++++++++++
1 file changed, 58 insertions(+)
create mode 100644 Documentation/devicetree/bindings/rtc/ricoh,r2223x.yaml
diff --git a/Documentation/devicetree/bindings/rtc/ricoh,r2223x.yaml b/Documentation/devicetree/bindings/rtc/ricoh,r2223x.yaml
new file mode 100644
index 000000000000..e64a1ee378e6
--- /dev/null
+++ b/Documentation/devicetree/bindings/rtc/ricoh,r2223x.yaml
@@ -0,0 +1,58 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/rtc/ricoh,r2223x.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Ricoh R2223x Real-Time Clock
+
+maintainers:
+ - Heiko Schocher <hs@nabladev.com>
+
+allOf:
+ - $ref: rtc.yaml#
+
+properties:
+ compatible:
+ const: ricoh,r2223x
+
+ reg:
+ maxItems: 1
+
+ interrupts:
+ maxItems: 1
+
+ "#clock-cells":
+ const: 0
+
+ ricoh,eco-mode:
+ type: boolean
+ description:
+ Put the RTC into eco mode, which lowers its current consumption while
+ running from the backup supply. Set this on boards where the RTC is
+ expected to keep time on a small backup cell.
+
+ start-year: true
+
+required:
+ - compatible
+ - reg
+
+additionalProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/interrupt-controller/irq.h>
+
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ rtc@32 {
+ compatible = "ricoh,r2223x";
+ reg = <0x32>;
+ interrupts = <6 IRQ_TYPE_EDGE_FALLING>;
+ #clock-cells = <0>;
+ ricoh,eco-mode;
+ };
+ };
--
2.55.0
next prev parent 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 [PATCH v1 0/3] rtc: rs5c372: add Ricoh R2223x support Heiko Schocher
2026-08-24 11:04 ` Heiko Schocher [this message]
2026-08-24 11:08 ` [PATCH v1 1/3] dt-bindings: rtc: add ricoh,r2223x binding 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-2-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