From: sashiko-bot@kernel.org
To: "Bhargav Joshi" <j.bhargav.u@gmail.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH] dt-bindings: pinctrl: ti,dra7-iodelay: Convert to DT schema
Date: Mon, 13 Jul 2026 12:57:20 +0000 [thread overview]
Message-ID: <20260713125721.2E22D1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260713-ti-iodelay-v1-1-5f06d36c4aac@gmail.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The child node regex `^mmc.*_conf$` arbitrarily restricts I/O delay configuration nodes to those starting with 'mmc', even though the controller is generic.
- [Medium] The `pinctrl-pin-array` property is not marked as required within the child node schema.
--
--- Patch [1]: [PATCH] dt-bindings: pinctrl: ti,dra7-iodelay: Convert to DT schema ---
commit 59d5959fa2ce86d89ce637daf5f846ce2bedcb0d
Author: Bhargav Joshi <j.bhargav.u@gmail.com>
dt-bindings: pinctrl: ti,dra7-iodelay: Convert to DT schema
This commit converts the TI IODELAY controller bindings from plain text
to DT schema. It also adds documentation for child properties missing
from the original text bindings.
> diff --git a/Documentation/devicetree/bindings/pinctrl/ti,dra7-iodelay.yaml b/Documentation/devicetree/bindings/pinctrl/ti,dra7-iodelay.yaml
> new file mode 100644
> index 0000000000000..a399946ae8172
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pinctrl/ti,dra7-iodelay.yaml
[ ... ]
> +patternProperties:
> + ^mmc.*_conf$:
[Severity: Medium]
Looking at the patternProperties definition, does this regression arbitrarily
restrict delay configuration nodes to only those starting with mmc?
The commit message mentions that mmc pins are just an example of pins
needing dynamic configuration. If a device tree dynamically configures delay
for other pins, will this reject them as invalid?
Would it be better to use a more generic pattern?
> + type: object
> + additionalProperties: false
> + properties:
> + pinctrl-pin-array:
> + $ref: /schemas/types.yaml#/definitions/uint32-array
> + description: |
> + An array of 32-bit integers defining the pin delay configuration.
[Severity: Medium]
Could this regression allow incomplete configuration nodes to pass schema
validation?
Since pinctrl-pin-array is not marked as required, an empty child node would
pass dt_binding_check, but the driver expects this property to be present
to initialize the mapping. Should it be added to a required list within the
patternProperties block?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260713-ti-iodelay-v1-1-5f06d36c4aac@gmail.com?part=1
prev parent reply other threads:[~2026-07-13 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 12:42 [PATCH] dt-bindings: pinctrl: ti,dra7-iodelay: Convert to DT schema Bhargav Joshi
2026-07-13 12:57 ` 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=20260713125721.2E22D1F00A3A@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=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