From: sashiko-bot@kernel.org
To: "Bhargav Joshi" <j.bhargav.u@gmail.com>
Cc: devicetree@vger.kernel.org, mfd@lists.linux.dev, lee@kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 2/2] dt-bindings: mfd: ti,keystone-devctrl: Convert to DT schema
Date: Sat, 15 Aug 2026 19:00:40 +0000 [thread overview]
Message-ID: <20260815190040.7973A1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260816-ti-keystone-devctrl-v2-2-5ab1e13c15c1@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Unresolved phandle references in the YAML example cause `dt_binding_check` failures.
--
--- Patch [2]: [PATCH v2 2/2] dt-bindings: mfd: ti,keystone-devctrl: Convert to DT schema ---
commit 48184e73993f7287e1c95f939a5d488075736de6
Author: Bhargav Joshi <j.bhargav.u@gmail.com>
dt-bindings: mfd: ti,keystone-devctrl: Convert to DT schema
This commit converts the Texas Instruments Keystone Device State Control
binding from the legacy text format to a DT schema. It also adds simple-mfd
and missing bus properties while documenting child nodes.
> diff --git a/Documentation/devicetree/bindings/mfd/ti,keystone-devctrl.yaml b/Documentation/devicetree/bindings/mfd/ti,keystone-devctrl.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mfd/ti,keystone-devctrl.yaml
[ ... ]
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> +
> + device-state-control@2620000 {
> + compatible = "ti,keystone-devctrl", "syscon", "simple-mfd";
> + reg = <0x02620000 0x1000>;
[ ... ]
> + interrupt-controller@2a0 {
> + compatible = "ti,keystone-irq";
> + reg = <0x2a0 0x4>;
> + interrupts = <GIC_SPI 4 IRQ_TYPE_EDGE_RISING>;
> + interrupt-controller;
> + #interrupt-cells = <1>;
> + ti,syscon-dev = <&devctrl 0x2a0>;
[Severity: Low]
Will dtc fail to compile this example due to an unresolved phandle reference?
The previous text binding defined a devctrl: label for the parent node, but
it appears to have been dropped during the conversion.
> + };
> +
> + reset-controller@328 {
> + compatible = "ti,keystone-reset";
> + reg = <0x328 0x10>;
> + ti,syscon-pll = <&pllctrl 0xe4>;
[Severity: Low]
Does the example need a dummy pllctrl node or label to avoid validation
failures? It looks like &pllctrl is referenced here but not defined anywhere
in the example block.
> + ti,syscon-dev = <&devctrl 0x328>;
> + ti,wdt-list = <0>;
> + };
> + };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260816-ti-keystone-devctrl-v2-0-5ab1e13c15c1@gmail.com?part=2
prev parent reply other threads:[~2026-08-15 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 18:52 [PATCH v2 0/2] ti,keystone-devctrl: Convert to DT schema and DTS cleanups Bhargav Joshi
2026-08-15 18:52 ` [PATCH v2 1/2] ARM: dts: ti: keystone: Align devctrl child node names with dtschema Bhargav Joshi
2026-08-15 18:59 ` sashiko-bot
2026-08-15 18:53 ` [PATCH v2 2/2] dt-bindings: mfd: ti,keystone-devctrl: Convert to DT schema Bhargav Joshi
2026-08-15 19:00 ` 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=20260815190040.7973A1F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j.bhargav.u@gmail.com \
--cc=lee@kernel.org \
--cc=mfd@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.