From: Herve Codina <herve.codina@bootlin.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Herve Codina <herve.codina@bootlin.com>
Subject: [PATCH 0/3] rtc: pcf2127: Add support for output clock and disable the pcf2131 100th counter
Date: Mon, 2 Nov 2026 14:07:08 +0100 [thread overview]
Message-ID: <20261102130712.25104-1-herve.codina@bootlin.com> (raw)
Hi,
PCF2127, PCF2129, PCA2129 and PCF2131 provide a configurable output
clock. The first two patches in this series add support for this output
clock.
The third patch of the series disables the 100th counter available in
the PCF2131. This counter is enabled by default in the hardware but
100th seconds are not used by the RTC subsystem. Fully disabling it
allows to save energy when the RTC is powered by its battery without
any functional changes.
Best regards,
Hervé
Herve Codina (3):
dt-bindings: rtc: pcf2127: Add support for clkout clock
rtc: pcf2127: Add support for the clkout clock
rtc: pcf2127: Disable the 100th counter for PCF2131
.../devicetree/bindings/rtc/nxp,pcf2127.yaml | 6 +
drivers/rtc/rtc-pcf2127.c | 201 ++++++++++++++++++
2 files changed, 207 insertions(+)
--
2.56.0
next reply other threads:[~2026-11-02 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 13:07 Herve Codina [this message]
2026-11-02 13:07 ` [PATCH 1/3] dt-bindings: rtc: pcf2127: Add support for clkout clock Herve Codina
2026-11-02 19:32 ` Conor Dooley
2026-11-02 13:07 ` [PATCH 2/3] rtc: pcf2127: Add support for the " Herve Codina
2026-11-02 13:07 ` [PATCH 3/3] rtc: pcf2127: Disable the 100th counter for PCF2131 Herve Codina
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=20261102130712.25104-1-herve.codina@bootlin.com \
--to=herve.codina@bootlin.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 \
--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
all inboxes | Powered by JetHome®