From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Lad Prabhakar <prabhakar.csengg@gmail.com>
Cc: linux-renesas-soc@vger.kernel.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
linux-rtc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 3/4] dt-bindings: rtc: rzn1: add R-Car X5H support
Date: Sun, 27 Sep 2026 18:14:13 +0200 [thread overview]
Message-ID: <arlA1YuH709wjtHm@ninjato> (raw)
In-Reply-To: <CAMuHMdWy6ksspwvj8jRxf6_OATU5rS5p92KyG4+sEF+ag7S9NA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 309 bytes --]
> > + required:
> > + - interrupts
> > + - interrupt-names
> > +
>
> Sorry for missing this before: the "resets" property is
> completely missing.
Yes. Prabhakar, looking at the N2H and T2H DTSI files, I assume that
those also have resets for the RTC and only N1D has none?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-09-27 16:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 11:13 [PATCH v3 0/4] rtc: rzn1: cleanups, R-Car X5H enablement Wolfram Sang
2026-09-17 11:13 ` [PATCH v3 1/4] dt-bindings: rtc: rzn1: drop unneeded 'start-year' from example Wolfram Sang
2026-09-17 11:17 ` sashiko-bot
2026-09-17 11:13 ` [PATCH v3 2/4] dt-bindings: rtc: rzn1: add SoC names next to their IDs Wolfram Sang
2026-09-17 11:16 ` sashiko-bot
2026-09-17 11:13 ` [PATCH v3 3/4] dt-bindings: rtc: rzn1: add R-Car X5H support Wolfram Sang
2026-09-17 11:19 ` sashiko-bot
2026-09-17 12:35 ` Geert Uytterhoeven
2026-09-24 22:17 ` Rob Herring (Arm)
2026-09-25 7:43 ` Geert Uytterhoeven
2026-09-27 16:14 ` Wolfram Sang [this message]
2026-09-28 8:36 ` Geert Uytterhoeven
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=arlA1YuH709wjtHm@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=prabhakar.csengg@gmail.com \
--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