From: Shawn Guo <shawnguo@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: imx6qdl-udoo: Disable USB host to work around boot issues
Date: Thu, 5 May 2022 13:40:29 +0800 [thread overview]
Message-ID: <20220505054029.GY14615@dragon> (raw)
In-Reply-To: <20220501174713.103449-1-broonie@kernel.org>
On Sun, May 01, 2022 at 06:47:13PM +0100, Mark Brown wrote:
> Attempting to boot my Udoo Dual and Quad with mainline hangs during boot
> after printing:
>
> [ 3.270471] imx_usb 2184000.usb: No over current polarity defined
> [ 3.922502] mxs_phy 20c9000.usbphy: Data pin can't make good contact.
> [ 3.940097] imx_usb 2184200.usb: No over current polarity defined
>
> where imx_usb 2184200.usb is usbh1 in the DT. Adding debug prints to the
> code seems to show that we lock up at the first read in usbmisc_imx6q_init()
> which in combination with the above logging about the USB controllers
> suggests that we lock up on the first read in usbmisc_imx6q_init(). Looking
> at some of the other i.MX6 boards and the warning messages that are being
> printed suggests that there is bitrot in the DTS for the device so disable
> it for now, with it disabled the board boots successfully. Clearly this is
> not a real fix, but it does allow some use of the board with mainline.
>
> Similar behaviour is seen all the way back as far as v4.19, I tried going
> back to when the board was added but had toolchain issues. Vendor provided
> binaries seem fine on the boards so it seems likely that the hardware is
> fine and the issue is with some combination of the DT and kernel. This
> should obviously be resolved properly but for now this at least allows
> the kernel to boot with reduced functionality on these systems.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
Applied, thanks!
_______________________________________________
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:[~2022-05-05 5:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 17:47 [PATCH] ARM: dts: imx6qdl-udoo: Disable USB host to work around boot issues Mark Brown
2022-05-01 22:35 ` Fabio Estevam
2022-05-02 1:11 ` Fabio Estevam
2022-05-05 5:40 ` Shawn Guo [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=20220505054029.GY14615@dragon \
--to=shawnguo@kernel.org \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=s.hauer@pengutronix.de \
/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.