linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: shawnguo@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, aford173@gmail.com,
	Fabio Estevam <festevam@denx.de>
Subject: [PATCH 2/2] arm64: dts: imx8mm-beacon-baseboard: Remove usbotg2 pinctrl-names
Date: Wed,  9 Aug 2023 18:24:10 -0300	[thread overview]
Message-ID: <20230809212410.2865024-2-festevam@gmail.com> (raw)
In-Reply-To: <20230809212410.2865024-1-festevam@gmail.com>

From: Fabio Estevam <festevam@denx.de>

There is no pinctrl description under usbotg2 node, so remove the unneeded
'pinctrl-names' property.

This fixes the following schema warning:

imx8mm-beacon-kit.dtb: usb@32e50000: 'pinctrl-0' is a dependency of 'pinctrl-names'

Signed-off-by: Fabio Estevam <festevam@denx.de>
---
 arch/arm64/boot/dts/freescale/imx8mm-beacon-baseboard.dtsi | 1 -
 1 file changed, 1 deletion(-)

diff --git a/arch/arm64/boot/dts/freescale/imx8mm-beacon-baseboard.dtsi b/arch/arm64/boot/dts/freescale/imx8mm-beacon-baseboard.dtsi
index d5c6fc68d656..b10e2a703a44 100644
--- a/arch/arm64/boot/dts/freescale/imx8mm-beacon-baseboard.dtsi
+++ b/arch/arm64/boot/dts/freescale/imx8mm-beacon-baseboard.dtsi
@@ -289,7 +289,6 @@ &usbotg1 {
 };
 
 &usbotg2 {
-	pinctrl-names = "default";
 	disable-over-current;
 	dr_mode = "host";
 	status = "okay";
-- 
2.34.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-08-09 21:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 21:24 [PATCH 1/2] arm64: dts: imx8mm-emcon: Remove iomuxc pinctrl-names Fabio Estevam
2023-08-09 21:24 ` Fabio Estevam [this message]
2023-08-10  2:36   ` [PATCH 2/2] arm64: dts: imx8mm-beacon-baseboard: Remove usbotg2 pinctrl-names Adam Ford
2023-08-11 14:40 ` [PATCH 1/2] arm64: dts: imx8mm-emcon: Remove iomuxc pinctrl-names Shawn Guo

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=20230809212410.2865024-2-festevam@gmail.com \
    --to=festevam@gmail.com \
    --cc=aford173@gmail.com \
    --cc=festevam@denx.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=shawnguo@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).