Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Wolfram Sang" <wsa+renesas@sang-engineering.com>
Cc: "Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	wsa+renesas@sang-engineering.com, conor+dt@kernel.org,
	devicetree@vger.kernel.org, robh@kernel.org,
	linux-rtc@vger.kernel.org
Subject: Re: [PATCH 3/6] dt-bindings: rtc: rzn1: interrupts are not required
Date: Mon, 14 Sep 2026 21:29:36 +0000	[thread overview]
Message-ID: <20260914212936.6C56B1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260914211826.73727-11-wsa+renesas@sang-engineering.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] Globally removing `interrupts` and `interrupt-names` from `required` weakens schema validation for existing SoCs.
- [Medium] Making `interrupts` and `interrupt-names` optional without adding a schema dependency allows incomplete interrupt specifications.
--

commit 963405de649fb7157801d57b7a47cf959108ca2c
Author: Wolfram Sang <wsa+renesas@sang-engineering.com>

dt-bindings: rtc: rzn1: interrupts are not required

This commit drops the interrupts and interrupt-names properties from the
required list in the rzn1-rtc binding. This change is made to support an
upcoming SoC where interrupts are not wired to the RTC.

> diff --git a/Documentation/devicetree/bindings/rtc/renesas,rzn1-rtc.yaml b/Documentation/devicetree/bindings/rtc/renesas,rzn1-rtc.yaml
> index 7ea77cd0bee15..b426a34958d6d 100644
> --- a/Documentation/devicetree/bindings/rtc/renesas,rzn1-rtc.yaml
> +++ b/Documentation/devicetree/bindings/rtc/renesas,rzn1-rtc.yaml
> @@ -52,8 +52,6 @@ properties:
>  required:
>    - compatible
>    - reg
> -  - interrupts
> -  - interrupt-names

[Severity: Medium]
Does globally removing these properties weaken schema validation for existing
SoCs? Device trees for existing SoCs where interrupts are physically wired
could now incorrectly omit the interrupts and silently pass the schema
checker, resulting in incomplete hardware descriptions.

To accommodate the new SoC without affecting existing ones, should we
conditionally require these properties for the older compatible strings
using an allOf -> if -> then block?

[Severity: Medium]
By making these properties optional independently, could this allow
incomplete interrupt specifications? If a device tree specifies interrupts
but omits interrupt-names, schema validation will pass. However, the driver
uses platform_get_irq_byname_optional(), which will fail with -EINVAL at
runtime if names are missing, silently disabling alarm functionality.

Would it be better to include a dependencies block (e.g.,
interrupts: [ interrupt-names ]) to ensure complete descriptions when
interrupts are provided?

>    - clocks
>    - clock-names
>    - power-domains

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260914211826.73727-8-wsa+renesas@sang-engineering.com?part=3

  reply	other threads:[~2026-09-14 21:29 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 [this message]
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 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=20260914212936.6C56B1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=wsa+renesas@sang-engineering.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