From: Tony Lindgren <tony@atomide.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: Unify pinctrl-single pin group nodes for stingray
Date: Fri, 19 May 2023 14:16:11 +0300 [thread overview]
Message-ID: <20230519111611.GX14287@atomide.com> (raw)
In-Reply-To: <20230519072522.52263-1-tony@atomide.com>
* Tony Lindgren <tony@atomide.com> [230519 07:27]:
> We want to unify the pinctrl-single pin group nodes as these will add
> make dtbs checks errors when pinctrl-single yaml binding is merged.
...
> --- a/arch/arm64/boot/dts/broadcom/stingray/stingray-pinctrl.dtsi
> +++ b/arch/arm64/boot/dts/broadcom/stingray/stingray-pinctrl.dtsi
> @@ -299,7 +299,7 @@ spi1_pins: pinmux_spi1_sck_nand {
> >;
> };
>
> - nuart_pins: pinmux_uart0_sin_nitro {
> + nuart_pins: uart0-sin-nitro-pins {
> pinctrl-single,pins = <
> 0x20c MODE_NITRO /* nuart_rxd */
> 0x210 MODE_NITRO /* nuart_txd */
> @@ -319,7 +319,7 @@ uart0_pins: pinumux_uart0_sin_nand {
Looks like I missed the misspelled "pinumux" node, will send out v2
version of the patch.
Regards,
Tony
prev parent reply other threads:[~2023-05-19 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 7:25 [PATCH] arm64: dts: Unify pinctrl-single pin group nodes for stingray Tony Lindgren
2023-05-19 11:16 ` Tony Lindgren [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=20230519111611.GX14287@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.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;
as well as URLs for NNTP newsgroup(s).