From: Conor Dooley <conor@kernel.org>
To: Ze Huang <huangze@whut.edu.cn>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Chen Wang <unicorn_wang@outlook.com>,
Inochi Amaoto <inochiama@gmail.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, sophgo@lists.linux.dev
Subject: Re: [PATCH] dt-bindings: pinctrl: k230: fix child node name patterns
Date: Tue, 27 May 2025 15:36:52 +0100 [thread overview]
Message-ID: <20250527-activism-container-4a9da77a8da1@spud> (raw)
In-Reply-To: <20250527-k230-binding-fix-v1-1-3c18ae5221ab@whut.edu.cn>
[-- Attachment #1: Type: text/plain, Size: 2304 bytes --]
On Tue, May 27, 2025 at 12:23:35AM +0800, Ze Huang wrote:
> Rename child node name patterns to align with conventions.
>
> uart0-pins => uart0-cfg
> uart0-cfg uart0-pins
>
> This avoids potential confusion and improves consistency with existing
> bindings like sophgo,sg2042-pinctrl and starfive,jh7110-aon-pinctrl.
>
> Fixes: 561f3e9d21a1 ("dt-bindings: pinctrl: Add support for canaan,k230 SoC")
You're changing something merged in October of last year, which is an
ABI break, for what seems like a cosmetic change to me. What makes this
worth it? Consistency with some devices by other vendors isn't a strong
argument I don't think.
> Signed-off-by: Ze Huang <huangze@whut.edu.cn>
> ---
> .../devicetree/bindings/pinctrl/canaan,k230-pinctrl.yaml | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/pinctrl/canaan,k230-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/canaan,k230-pinctrl.yaml
> index 0b462eb6dfe169a292bf716503c03d029f1ac7ee..f4e0da0bf7fa30af5132644109dbd371ddfc0228 100644
> --- a/Documentation/devicetree/bindings/pinctrl/canaan,k230-pinctrl.yaml
> +++ b/Documentation/devicetree/bindings/pinctrl/canaan,k230-pinctrl.yaml
> @@ -22,7 +22,7 @@ properties:
> maxItems: 1
>
> patternProperties:
> - '-pins$':
> + '-cfg$':
> type: object
> additionalProperties: false
> description:
> @@ -30,7 +30,7 @@ patternProperties:
> pinctrl groups available on the machine.
>
> patternProperties:
> - '-cfg$':
> + '-pins$':
> type: object
> allOf:
> - $ref: /schemas/pinctrl/pincfg-node.yaml
> @@ -112,8 +112,8 @@ examples:
> compatible = "canaan,k230-pinctrl";
> reg = <0x91105000 0x100>;
>
> - uart2-pins {
> - uart2-pins-cfg {
> + uart2-cfg {
> + uart2-pins {
> pinmux = <0x503>, /* uart2 txd */
> <0x603>; /* uart2 rxd */
> slew-rate = <0>;
>
> ---
> base-commit: 0a4b866d08c6adaea2f4592d31edac6deeb4dcbd
> change-id: 20250526-k230-binding-fix-3125ff43f930
>
> Best regards,
> --
> Ze Huang <huangze@whut.edu.cn>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-05-27 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 16:23 [PATCH] dt-bindings: pinctrl: k230: fix child node name patterns Ze Huang
2025-05-27 14:36 ` Conor Dooley [this message]
2025-05-27 15:07 ` Ze Huang
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=20250527-activism-container-4a9da77a8da1@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=huangze@whut.edu.cn \
--cc=inochiama@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sophgo@lists.linux.dev \
--cc=unicorn_wang@outlook.com \
/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