From: Owen O'Hehir <oo.hehir@gmail.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-rtc@vger.kernel.org
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Emil Renner Berthing <kernel@esmil.dk>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Philipp Zabel <p.zabel@pengutronix.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org,
Hal Feng <hal.feng@starfivetech.com>,
"ziv.xu" <ziv.xu@starfivetech.com>,
Conor Dooley <conor@kernel.org>
Subject: [PATCH 1/3] dt-bindings: rtc: Add StarFive JH7110 RTC
Date: Fri, 6 Nov 2026 17:55:58 +0000 [thread overview]
Message-ID: <20261106175600.3877614-2-oo.hehir@gmail.com> (raw)
In-Reply-To: <20261106175600.3877614-1-oo.hehir@gmail.com>
Describe the RTC in the always-on domain of the StarFive JH7110 SoC.
Signed-off-by: Owen O'Hehir <oo.hehir@gmail.com>
---
.../bindings/rtc/starfive,jh7110-rtc.yaml | 85 +++++++++++++++++++
1 file changed, 85 insertions(+)
create mode 100644 Documentation/devicetree/bindings/rtc/starfive,jh7110-rtc.yaml
diff --git a/Documentation/devicetree/bindings/rtc/starfive,jh7110-rtc.yaml b/Documentation/devicetree/bindings/rtc/starfive,jh7110-rtc.yaml
new file mode 100644
index 000000000..95edddea1
--- /dev/null
+++ b/Documentation/devicetree/bindings/rtc/starfive,jh7110-rtc.yaml
@@ -0,0 +1,85 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/rtc/starfive,jh7110-rtc.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: StarFive JH7110 Real Time Clock
+
+maintainers:
+ - Alexandre Belloni <alexandre.belloni@bootlin.com>
+
+description:
+ The RTC in the always-on domain of the StarFive JH7110 SoC. It counts BCD
+ time and date from a 32.768 kHz clock and has an alarm, a frequency offset
+ adjustment and millisecond and one-second pulse outputs.
+
+allOf:
+ - $ref: rtc.yaml#
+
+properties:
+ compatible:
+ const: starfive,jh7110-rtc
+
+ reg:
+ maxItems: 1
+
+ interrupts:
+ items:
+ - description: Millisecond pulse
+ - description: One-second pulse
+ - description: Alarm and calibration events
+
+ interrupt-names:
+ items:
+ - const: ms-pulse
+ - const: sec-pulse
+ - const: rtc
+
+ clocks:
+ items:
+ - description: APB bus clock
+ - description: Calibration reference clock
+ - description: 32.768 kHz counter clock
+
+ clock-names:
+ items:
+ - const: apb
+ - const: cal
+ - const: 32k
+
+ resets:
+ items:
+ - description: 32.768 kHz counter domain reset
+ - description: APB bus reset
+ - description: Calibration reset
+
+required:
+ - compatible
+ - reg
+ - interrupts
+ - interrupt-names
+ - clocks
+ - clock-names
+ - resets
+
+unevaluatedProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/clock/starfive,jh7110-crg.h>
+ #include <dt-bindings/reset/starfive,jh7110-crg.h>
+
+ rtc@17040000 {
+ compatible = "starfive,jh7110-rtc";
+ reg = <0x17040000 0x10000>;
+ interrupts = <10>, <11>, <12>;
+ interrupt-names = "ms-pulse", "sec-pulse", "rtc";
+ clocks = <&aoncrg JH7110_AONCLK_RTC_APB>,
+ <&aoncrg JH7110_AONCLK_RTC_CAL>,
+ <&aoncrg JH7110_AONCLK_RTC_32K>;
+ clock-names = "apb", "cal", "32k";
+ resets = <&aoncrg JH7110_AONRST_RTC_32K>,
+ <&aoncrg JH7110_AONRST_RTC_APB>,
+ <&aoncrg JH7110_AONRST_RTC_CAL>;
+ };
--
2.43.0
next prev parent reply other threads:[~2026-11-06 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 17:55 [PATCH 0/3] rtc: Add StarFive JH7110 RTC support Owen O'Hehir
2026-11-06 17:55 ` Owen O'Hehir [this message]
2026-11-06 18:16 ` [PATCH 1/3] dt-bindings: rtc: Add StarFive JH7110 RTC Conor Dooley
2026-11-06 17:55 ` [PATCH 2/3] rtc: Add StarFive JH7110 RTC driver Owen O'Hehir
2026-11-06 17:56 ` [PATCH 3/3] riscv: dts: starfive: jh7110: Add the RTC node Owen O'Hehir
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=20261106175600.3877614-2-oo.hehir@gmail.com \
--to=oo.hehir@gmail.com \
--cc=alex@ghiti.fr \
--cc=alexandre.belloni@bootlin.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hal.feng@starfivetech.com \
--cc=kernel@esmil.dk \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=ziv.xu@starfivetech.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®