From: sashiko-bot@kernel.org
To: "Long Zhao" <longzhao@ambarella.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/4] dt-bindings: pinctrl: add Ambarella CV75 pinctrl
Date: Fri, 14 Aug 2026 06:35:41 +0000 [thread overview]
Message-ID: <20260814063546.AB5351F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260814-cv75-v4-b-v4-1-ef2e83ec0eac@ambarella.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The binding schema prevents configuring bias and drive strength for GPIO pins because 'function' is strictly required (with no 'gpio' option), the 'groups' enum lacks GPIO options, and the 'pins' property is forbidden.
--
--- Patch [1]: [PATCH v4 1/4] dt-bindings: pinctrl: add Ambarella CV75 pinctrl ---
commit a8e38fe4533be470b102e4e747568db3d0143b1a
Author: Long Zhao <longzhao@ambarella.com>
dt-bindings: pinctrl: add Ambarella CV75 pinctrl
Document the CV75 pin controller binding using generic function and
groups properties for pinmux configuration.
> diff --git a/Documentation/devicetree/bindings/pinctrl/ambarella,cv75-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/ambarella,cv75-pinctrl.yaml
> new file mode 100644
> index 0000000000000..9d65da32d3d28
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pinctrl/ambarella,cv75-pinctrl.yaml
[ ... ]
> +patternProperties:
> + "^[a-z0-9-]+-pins$":
> + type: object
> + allOf:
> + - $ref: pinmux-node.yaml#
> + - $ref: pincfg-node.yaml#
> + additionalProperties: false
[Severity: Medium]
Will this combination of 'additionalProperties: false' and omitting a
definition for 'pins' prevent configuring individual pins?
This appears to reject the standard 'pins' property, meaning users cannot
specify pin-level configurations for GPIOs.
> +
> + properties:
> + function:
[ ... ]
> + drive-strength:
> + enum: [3, 4, 5, 6, 7, 8, 9, 12]
> +
> + required:
> + - function
> + - groups
[Severity: Medium]
Does requiring both 'function' and 'groups' unconditionally prevent
config-only nodes, such as configuring bias or drive strength for individual
GPIO pins?
Since 'gpio' is not an option in the 'function' enum, and 'pins' is blocked
by the earlier 'additionalProperties: false', it seems impossible to define a
valid node for GPIO configuration without incorrectly multiplexing the pin to a
peripheral function.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260814-cv75-v4-b-v4-0-ef2e83ec0eac@ambarella.com?part=1
next prev parent reply other threads:[~2026-08-14 6:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 6:25 [PATCH v4 0/4] Ambarella CV75: pinctrl and PL061 GPIO Long Zhao via B4 Relay
2026-08-14 6:25 ` Long Zhao
2026-08-14 6:25 ` [PATCH v4 1/4] dt-bindings: pinctrl: add Ambarella CV75 pinctrl Long Zhao via B4 Relay
2026-08-14 6:25 ` Long Zhao
2026-08-14 6:35 ` sashiko-bot [this message]
2026-08-14 6:25 ` [PATCH v4 2/4] dt-bindings: gpio: pl061: add Ambarella CV75 variant Long Zhao via B4 Relay
2026-08-14 6:25 ` Long Zhao
2026-08-14 6:25 ` [PATCH v4 3/4] gpio: pl061: add Ambarella CV75 register layout variant Long Zhao via B4 Relay
2026-08-14 6:25 ` Long Zhao
2026-08-14 6:35 ` sashiko-bot
2026-08-14 6:25 ` [PATCH v4 4/4] pinctrl: ambarella: add CV75 pin controller Long Zhao via B4 Relay
2026-08-14 6:25 ` Long Zhao
2026-08-14 6:40 ` sashiko-bot
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=20260814063546.AB5351F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=longzhao@ambarella.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 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.