Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Bhargav Joshi" <j.bhargav.u@gmail.com>
Cc: linux-rtc@vger.kernel.org,
	"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 3/3] dt-bindings: rtc: ti,omap-rtc: Convert to DT schema
Date: Fri, 24 Jul 2026 21:08:26 +0000	[thread overview]
Message-ID: <20260724210826.EC1171F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260725-ti-omap-rtc-v2-3-13f765ca96b3@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Missing phandle label in the YAML example causing a dtc compilation error.
--

--- Patch [3]: [PATCH v2 3/3] dt-bindings: rtc: ti,omap-rtc: Convert to DT schema ---
commit 0cee4f860a851104188182b49417909d1f275491
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. It also marks 'ti,hwmods' as deprecated
since it is no longer used.

> 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..326d5ad972922
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/rtc/ti,omap-rtc.yaml

[ ... ]

> +  - |
> +    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 {

[Severity: Low]
Will this cause a dtc compilation error during make dt_binding_check? 

The pinctrl-0 property above references <&ext_wakeup>, but it appears the 
label "ext_wakeup:" was dropped from this child node during the conversion 
from the text binding.

> +            pins = "ext_wakeup0";
> +            input-enable;
> +            ti,active-high;
> +        };
> +    };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260725-ti-omap-rtc-v2-0-13f765ca96b3@gmail.com?part=3

      reply	other threads:[~2026-07-24 21:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 21:01 [PATCH v2 0/3] dt-bindings: rtc: ti,omap-rtc: Convert to DT schema and cleanups Bhargav Joshi
2026-07-24 21:01 ` [PATCH v2 1/3] ARM: dts: ti: am57xx-idk-common: Remove unused ext-clk-src property Bhargav Joshi
2026-07-24 21:11   ` sashiko-bot
2026-07-24 21:01 ` [PATCH v2 2/3] ARM: dts: ti: am335x-shc: Remove unused ti,no-init property Bhargav Joshi
2026-07-24 21:05   ` sashiko-bot
2026-07-24 21:01 ` [PATCH v2 3/3] dt-bindings: rtc: ti,omap-rtc: Convert to DT schema Bhargav Joshi
2026-07-24 21:08   ` 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=20260724210826.EC1171F000E9@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