From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-rtc@vger.kernel.org
Subject: Re: [PATCH 4/6] rtc: rzn1: make interrupts optional
Date: Tue, 15 Sep 2026 11:17:37 +0200 [thread overview]
Message-ID: <aqkNLBOXfN4w85I8@shikoro> (raw)
In-Reply-To: <20260914211826.73727-12-wsa+renesas@sang-engineering.com>
[-- Attachment #1: Type: text/plain, Size: 442 bytes --]
On Mon, Sep 14, 2026 at 11:18:29PM +0200, Wolfram Sang wrote:
> If no interrupts are specified, alarm handling will just be disabled. No
> need to bail out. Instead of juggling with 4 different static rtc_ops
> for all {subu|scmp}_{no_}alarm cases, a single non-static rtc_ops is
> chosen which is adapted during probe().
I kinda expected it. Sashiko complained enough abou the non-const
rtc_ops, so I will switch to multiple const ones...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-09-15 9:17 UTC|newest]
Thread overview: 15+ 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-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-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-15 9:55 ` Lad, Prabhakar
2026-09-15 16:54 ` Conor Dooley
2026-09-16 7:32 ` Wolfram Sang
2026-09-14 21:18 ` [PATCH 4/6] rtc: rzn1: make interrupts optional Wolfram Sang
2026-09-15 9:17 ` 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:18 ` [PATCH 6/6] " Wolfram Sang
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=aqkNLBOXfN4w85I8@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=miquel.raynal@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