From: Conor Dooley <conor@kernel.org>
To: Heiko Schocher <hs@nabladev.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
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
Subject: Re: [PATCH v1 1/3] dt-bindings: rtc: add ricoh,r2223x binding
Date: Mon, 24 Aug 2026 17:26:59 +0100 [thread overview]
Message-ID: <20260824-endorphin-gotten-f1271d46ab93@spud> (raw)
In-Reply-To: <20260824110452.4038870-2-hs@nabladev.com>
[-- Attachment #1: Type: text/plain, Size: 600 bytes --]
On Mon, Aug 24, 2026 at 01:04:24PM +0200, Heiko Schocher wrote:
> 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>
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: not-applicable
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-08-24 16:27 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 ` [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 [this message]
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=20260824-endorphin-gotten-f1271d46ab93@spud \
--to=conor@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hs@nabladev.com \
--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