Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Bhargav Joshi" <j.bhargav.u@gmail.com>
Cc: conor+dt@kernel.org, linux-rtc@vger.kernel.org,
	devicetree@vger.kernel.org,
	"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	robh@kernel.org
Subject: Re: [PATCH v3 4/4] dt-bindings: rtc: ti,omap-rtc: Convert to DT schema
Date: Tue, 04 Aug 2026 17:30:18 +0000	[thread overview]
Message-ID: <20260804173018.91A501F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260804-ti-omap-rtc-v3-4-ba3bbd8af570@gmail.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] The `pattern` constraint on `pins` is bypassed because it is applied directly to an array property, rather than its items.
- [Low] The example contains an undefined label `ext_wakeup`, causing a dtc compilation error.
--

--- Patch [4]: [PATCH v3 4/4] dt-bindings: rtc: ti,omap-rtc: Convert to DT schema ---
commit 37b8c1cde7af9ea6b7fed4b7f431ec999b775ef6
Author: Bhargav Joshi <j.bhargav.u@gmail.com>

dt-bindings: rtc: ti,omap-rtc: Convert to DT schema

Convert the Texas Instruments OMAP Real Time Clock (RTC) binding from
the legacy text format to the DT schema. Mark 'ti,hwmods' as deprecated
as it is no longer used, it is kept to support legacy boards.

> diff --git a/Documentation/devicetree/bindings/rtc/ti,omap-rtc.yaml b/Documentation/devicetree/bindings/rtc/ti,omap-rtc.yaml
> new file mode 100644
> index 0000000000000..02b3c23cf4350
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/rtc/ti,omap-rtc.yaml
[ ... ]
> +patternProperties:
> +  "^ext-wakeup(-[0-9]+)?$":
> +    type: object
> +
> +    description:
> +      Child node describing external wakeup pin configuration.
> +
> +    properties:
> +      pins:
> +        pattern: '^ext_wakeup[0-3]$'

[Severity: Low]
Does this pattern constraint actually apply? Because pins is a string-array,
the pattern keyword directly on the property is ignored by the JSON schema
validator. It needs to be nested under items: { pattern: '^ext_wakeup[0-3]$' }
to validate the array elements.

[ ... ]
> +  - |
> +    rtc@0 {
> +        compatible = "ti,am3352-rtc", "ti,da830-rtc";
> +        reg = <0x0 0x1000>;
> +        interrupts = <75>, <76>;
> +        system-power-controller;
> +        clocks = <&clk_32k_rtc>, <&clk_32768_ck>;
> +        clock-names = "ext-clk", "int-clk";
> +
> +        pinctrl-0 = <&ext_wakeup>;
> +        pinctrl-names = "default";
> +
> +        ext-wakeup {
> +            pins = "ext_wakeup0";

[Severity: Low]
Will this example compile with dtc? The pinctrl-0 property references
<&ext_wakeup>, but the ext-wakeup subnode here is missing the ext_wakeup:
label that was present in the legacy text binding, which will cause a dtc
compilation error.

> +            input-enable;
> +            ti,active-high;
> +        };
> +    };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260804-ti-omap-rtc-v3-0-ba3bbd8af570@gmail.com?part=4

      reply	other threads:[~2026-08-04 17:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 17:05 [PATCH v3 0/4] dt-bindings: rtc: ti,omap-rtc: Convert to DT schema and cleanups Bhargav Joshi
2026-08-04 17:05 ` [PATCH v3 1/4] ARM: dts: ti: am57xx-idk-common: Remove unused ext-clk-src property Bhargav Joshi
2026-08-04 17:13   ` sashiko-bot
2026-08-04 17:05 ` [PATCH v3 2/4] ARM: dts: ti: am335x-shc: Remove unused ti,no-init property Bhargav Joshi
2026-08-04 17:12   ` sashiko-bot
2026-08-04 17:05 ` [PATCH v3 3/4] ARM: dts: omap: dra7: add da830 fallback to am3352 rtc compatible string Bhargav Joshi
2026-08-04 17:16   ` sashiko-bot
2026-08-04 17:05 ` [PATCH v3 4/4] dt-bindings: rtc: ti,omap-rtc: Convert to DT schema Bhargav Joshi
2026-08-04 17:30   ` sashiko-bot [this message]

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=20260804173018.91A501F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=j.bhargav.u@gmail.com \
    --cc=linux-rtc@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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