From: Alexandre Torgue <alexandre.torgue@st.com>
To: Benjamin Gaignard <benjamin.gaignard@st.com>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>
Cc: devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: stm32: remove "@" from stm32f7 pinmux groups
Date: Wed, 4 Dec 2019 16:23:15 +0100 [thread overview]
Message-ID: <f277b73f-716c-0746-73b8-45a8096d0bff@st.com> (raw)
In-Reply-To: <20191125121244.19591-1-benjamin.gaignard@st.com>
Hi Benjamin
On 11/25/19 1:12 PM, Benjamin Gaignard wrote:
> Replace all "@" by "_" in pinmux groups for stm32f7 family.
> This avoid errors when using yaml to check the bindings.
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
> ---
> arch/arm/boot/dts/stm32f7-pinctrl.dtsi | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/arch/arm/boot/dts/stm32f7-pinctrl.dtsi b/arch/arm/boot/dts/stm32f7-pinctrl.dtsi
> index 9314128df185..5271df1017cb 100644
> --- a/arch/arm/boot/dts/stm32f7-pinctrl.dtsi
> +++ b/arch/arm/boot/dts/stm32f7-pinctrl.dtsi
> @@ -127,7 +127,7 @@
> st,bank-name = "GPIOK";
> };
>
> - cec_pins_a: cec@0 {
> + cec_pins_a: cec_0 {
You fix a warning by adding a new one. Please use "cec-0" instead of
"cec_0". To be done for all changes in this file.
regards
Alex
> pins {
> pinmux = <STM32_PINMUX('A', 15, AF4)>; /* HDMI CEC */
> slew-rate = <0>;
> @@ -136,7 +136,7 @@
> };
> };
>
> - usart1_pins_a: usart1@0 {
> + usart1_pins_a: usart1_0 {
> pins1 {
> pinmux = <STM32_PINMUX('A', 9, AF7)>; /* USART1_TX */
> bias-disable;
> @@ -149,7 +149,7 @@
> };
> };
>
> - usart1_pins_b: usart1@1 {
> + usart1_pins_b: usart1_1 {
> pins1 {
> pinmux = <STM32_PINMUX('A', 9, AF7)>; /* USART1_TX */
> bias-disable;
> @@ -162,7 +162,7 @@
> };
> };
>
> - i2c1_pins_b: i2c1@0 {
> + i2c1_pins_b: i2c1_0 {
> pins {
> pinmux = <STM32_PINMUX('B', 9, AF4)>, /* I2C1 SDA */
> <STM32_PINMUX('B', 8, AF4)>; /* I2C1 SCL */
> @@ -172,7 +172,7 @@
> };
> };
>
> - usbotg_hs_pins_a: usbotg-hs@0 {
> + usbotg_hs_pins_a: usbotg-hs_0 {
> pins {
> pinmux = <STM32_PINMUX('H', 4, AF10)>, /* OTG_HS_ULPI_NXT */
> <STM32_PINMUX('I', 11, AF10)>, /* OTG_HS_ULPI_DIR */
> @@ -192,7 +192,7 @@
> };
> };
>
> - usbotg_hs_pins_b: usbotg-hs@1 {
> + usbotg_hs_pins_b: usbotg-hs_1 {
> pins {
> pinmux = <STM32_PINMUX('H', 4, AF10)>, /* OTG_HS_ULPI_NXT */
> <STM32_PINMUX('C', 2, AF10)>, /* OTG_HS_ULPI_DIR */
> @@ -212,7 +212,7 @@
> };
> };
>
> - usbotg_fs_pins_a: usbotg-fs@0 {
> + usbotg_fs_pins_a: usbotg-fs_0 {
> pins {
> pinmux = <STM32_PINMUX('A', 10, AF10)>, /* OTG_FS_ID */
> <STM32_PINMUX('A', 11, AF10)>, /* OTG_FS_DM */
> @@ -223,7 +223,7 @@
> };
> };
>
> - sdio_pins_a: sdio_pins_a@0 {
> + sdio_pins_a: sdio_pins_a_0 {
> pins {
> pinmux = <STM32_PINMUX('C', 8, AF12)>, /* SDMMC1 D0 */
> <STM32_PINMUX('C', 9, AF12)>, /* SDMMC1 D1 */
> @@ -236,7 +236,7 @@
> };
> };
>
> - sdio_pins_od_a: sdio_pins_od_a@0 {
> + sdio_pins_od_a: sdio_pins_od_a_0 {
> pins1 {
> pinmux = <STM32_PINMUX('C', 8, AF12)>, /* SDMMC1 D0 */
> <STM32_PINMUX('C', 9, AF12)>, /* SDMMC1 D1 */
> @@ -254,7 +254,7 @@
> };
> };
>
> - sdio_pins_b: sdio_pins_b@0 {
> + sdio_pins_b: sdio_pins_b_0 {
> pins {
> pinmux = <STM32_PINMUX('G', 9, AF11)>, /* SDMMC2 D0 */
> <STM32_PINMUX('G', 10, AF11)>, /* SDMMC2 D1 */
> @@ -267,7 +267,7 @@
> };
> };
>
> - sdio_pins_od_b: sdio_pins_od_b@0 {
> + sdio_pins_od_b: sdio_pins_od_b_0 {
> pins1 {
> pinmux = <STM32_PINMUX('G', 9, AF11)>, /* SDMMC2 D0 */
> <STM32_PINMUX('G', 10, AF11)>, /* SDMMC2 D1 */
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-12-04 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 12:12 [PATCH] ARM: dts: stm32: remove "@" from stm32f7 pinmux groups Benjamin Gaignard
2019-11-25 12:12 ` [PATCH] ARM: dts: stm32: remove "@" from stm32f4 " Benjamin Gaignard
2019-12-04 15:24 ` Alexandre Torgue
2019-12-04 15:23 ` Alexandre Torgue [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=f277b73f-716c-0746-73b8-45a8096d0bff@st.com \
--to=alexandre.torgue@st.com \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
/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).