Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Eduard Bostina" <egbostina@gmail.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3] dt-bindings: pinctrl: Convert TI DA850 pupd to DT schema
Date: Wed, 12 Aug 2026 10:46:23 +0000	[thread overview]
Message-ID: <20260812104623.CA8B91F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260812103621.1096140-1-egbostina@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The device tree schema for pin configuration subnodes fails to require the 'groups' property, allowing functionally empty nodes to silently pass validation.
--

--- Patch [1]: [PATCH v3] dt-bindings: pinctrl: Convert TI DA850 pupd to DT schema ---
commit 559e4d94cd353ab8a1d382bd65a364531394cb80
Author: Eduard Bostina <egbostina@gmail.com>

dt-bindings: pinctrl: Convert TI DA850 pupd to DT schema

Convert the Texas Instruments DA850/OMAP-L138/AM18x pullup/down
controller bindings to DT schema.

Link to v2: https://lore.kernel.org/all/20260811111023.721262-1-egbostina@gmail.com/
Link to v1: https://lore.kernel.org/all/20260811092057.687155-1-egbostina@gmail.com/

> diff --git a/Documentation/devicetree/bindings/pinctrl/ti,da850-pupd.yaml b/Documentation/devicetree/bindings/pinctrl/ti,da850-pupd.yaml
> new file mode 100644
> index 0000000000000..21d439e08d4b7
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pinctrl/ti,da850-pupd.yaml

[ ... ]

> @@ -28,17 +28,17 @@
> +patternProperties:
> +  "-groups$":
> +    type: object
> +    additionalProperties: false
> +    patternProperties:
> +      "^(disable|pull-(up|down))$":
> +        $ref: /schemas/pinctrl/pincfg-node.yaml#
> +        properties:
> +          groups:
> +            $ref: /schemas/types.yaml#/definitions/string-array
> +            description: An array of strings containing the name of a pin group.
> +            items:
> +              pattern: "^cp([0-9]|[1-2][0-9]|3[0-1])$"
> +          bias-disable: true
> +          bias-pull-up: true
> +          bias-pull-down: true
> +        additionalProperties: false

[Severity: Medium]
Should the groups property be explicitly listed as a required property in this
schema block?

Without a required: [ groups ] constraint here, a functionally empty node
could silently pass device tree schema validation. For example, a developer
could define a subnode like:

    pull-up {
        bias-pull-up;
    };

Since the kernel driver ignores nodes without target groups, the target
hardware pins would remain unconfigured at runtime without raising any schema
validation warnings.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260812103621.1096140-1-egbostina@gmail.com?part=1

  reply	other threads:[~2026-08-12 10:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12 10:36 [PATCH v3] dt-bindings: pinctrl: Convert TI DA850 pupd to DT schema Eduard Bostina
2026-08-12 10:46 ` sashiko-bot [this message]
2026-08-14 19:31 ` Rob Herring (Arm)
2026-08-14 20:17 ` Linus Walleij

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=20260812104623.CA8B91F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=egbostina@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