From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Conor Dooley <conor@kernel.org>
Cc: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>,
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 3/6] dt-bindings: rtc: rzn1: interrupts are not required
Date: Wed, 16 Sep 2026 09:32:52 +0200 [thread overview]
Message-ID: <aqpGH_VURXi8y569@ninjato> (raw)
In-Reply-To: <20260915-cultural-patriarch-9ad164b46cba@spud>
[-- Attachment #1: Type: text/plain, Size: 370 bytes --]
> > Maybe we can add a conditional schema check for SoCs where
> > interrupts{-names} are required.
>
> Yeah, I'd prefer this. If all current devices have the interrupt wired,
> there's little value in permitting them to not be populated and thereby
> lose the support for alarms.
Okay, I will refactor like this.
Thank you for your comments, everyone!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-09-16 7:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 21:18 [PATCH 0/6] rtc: rzn1: cleanups, no irq support, R-Car Gen5 enablement Wolfram Sang
2026-09-14 21:18 ` [PATCH 1/6] dt-bindings: rtc: rzn1: drop unneeded 'start-year' from example Wolfram Sang
2026-09-14 21:21 ` sashiko-bot
2026-09-15 9:52 ` Lad, Prabhakar
2026-09-15 16:55 ` Conor Dooley
2026-09-14 21:18 ` [PATCH 2/6] dt-bindings: rtc: rzn1: add SoC names next to their IDs Wolfram Sang
2026-09-14 21:20 ` sashiko-bot
2026-09-15 9:52 ` Lad, Prabhakar
2026-09-15 16:55 ` Conor Dooley
2026-09-14 21:18 ` [PATCH 3/6] dt-bindings: rtc: rzn1: interrupts are not required Wolfram Sang
2026-09-14 21:29 ` sashiko-bot
2026-09-15 9:55 ` Lad, Prabhakar
2026-09-15 16:54 ` Conor Dooley
2026-09-16 7:32 ` Wolfram Sang [this message]
2026-09-14 21:18 ` [PATCH 5/6] dt-bindings: rtc: rzn1: add R-Car X5H support Wolfram Sang
2026-09-14 21:29 ` sashiko-bot
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=aqpGH_VURXi8y569@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--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