[PATCH v2 4/4] riscv: dts: starfive: jh7110: Add the RTC node
E Shattow
e at freeshell.de
Sun Nov 8 19:37:34 PST 2026
Hi Owen,
On 11/8/26 13:28, Owen O'Hehir wrote:
> Tested on a VisionFive 2 v1.3B.
>
> Signed-off-by: Owen O'Hehir <oo.hehir at gmail.com>
> ---
> arch/riscv/boot/dts/starfive/jh7110.dtsi | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/arch/riscv/boot/dts/starfive/jh7110.dtsi b/arch/riscv/boot/dts/starfive/jh7110.dtsi
> index 82ea63f71..14f92b942 100644
> --- a/arch/riscv/boot/dts/starfive/jh7110.dtsi
> +++ b/arch/riscv/boot/dts/starfive/jh7110.dtsi
> @@ -1206,6 +1206,20 @@ pwrc: power-controller at 17030000 {
> #power-domain-cells = <1>;
> };
>
> + rtc: rtc at 17040000 {
> + compatible = "starfive,jh7110-rtc";
> + reg = <0x0 0x17040000 0x0 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>;
> + };
> +
> csi2rx: csi at 19800000 {
> compatible = "starfive,jh7110-csi2rx", "cdns,csi2rx";
> reg = <0x0 0x19800000 0x0 0x10000>;
Is status property applicable to SoC rtc? If not, then is 'rtc' label
appropriate when there's no status applicable?
Note that Mars CM / CM-Lite System-on-Modules may be used commonly with
board carriers which implement a battery-backed RTC on the I2C bus, and
so another 'rtc' label may be applicable, something to consider. The
initial Mars CM / CM-Lite dts ignores this because there is an
inconvenient I2C bus device address conflict of the SoM EEPROM and some
carrier boards' RTC, and the SoC RTC driver was not then present;
problems for a future self.
-E
More information about the linux-riscv
mailing list