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 1/3] dt-bindings: rtc: pcf2127: Add support for clkout clock
Date: Mon, 2 Nov 2026 14:07:09 +0100 [thread overview]
Message-ID: <20261102130712.25104-2-herve.codina@bootlin.com> (raw)
In-Reply-To: <20261102130712.25104-1-herve.codina@bootlin.com>
PCF2127, PCF2129, PCF2131 and PCA2129 provide a configurable output
clock on their CLKOUT pins.
Add support for this clock considering those devices as clock
providers.
Signed-off-by: Herve Codina <herve.codina@bootlin.com>
---
Documentation/devicetree/bindings/rtc/nxp,pcf2127.yaml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/rtc/nxp,pcf2127.yaml b/Documentation/devicetree/bindings/rtc/nxp,pcf2127.yaml
index 11fcf0ca1ae0..11c0bc04f304 100644
--- a/Documentation/devicetree/bindings/rtc/nxp,pcf2127.yaml
+++ b/Documentation/devicetree/bindings/rtc/nxp,pcf2127.yaml
@@ -27,6 +27,12 @@ properties:
interrupts:
maxItems: 1
+ "#clock-cells":
+ const: 0
+
+ clock-output-names:
+ maxItems: 1
+
start-year: true
reset-source: true
--
2.56.0
next prev parent 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 [PATCH 0/3] rtc: pcf2127: Add support for output clock and disable the pcf2131 100th counter Herve Codina
2026-11-02 13:07 ` Herve Codina [this message]
2026-11-02 19:32 ` [PATCH 1/3] dt-bindings: rtc: pcf2127: Add support for clkout clock 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-2-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®