public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: imx6qdl-udoo: Disable usbh1 to avoid kernel hang
Date: Thu, 22 Feb 2018 11:40:22 +0800	[thread overview]
Message-ID: <20180222034021.GE3217@dragon> (raw)
In-Reply-To: <1516278858-15464-1-git-send-email-fabio.estevam@nxp.com>

On Thu, Jan 18, 2018 at 10:34:18AM -0200, Fabio Estevam wrote:
> Currently the kernel hangs when USB Host1 is enabled due to the lack of
> support for controlling the USB hub clock and GPIO reset line.
> 
> Peter Chen has made several attempts to fix this problem, but his series
> has not been applied yet, so better disable USB host1 for now to avoid
> the kernel hang.
> 
> Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>

The commit log is not clear enough to tell why it works for v4.12 and
doesn't for 4.13 and later ones.

Shawn

> ---
>  arch/arm/boot/dts/imx6qdl-udoo.dtsi | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/arm/boot/dts/imx6qdl-udoo.dtsi b/arch/arm/boot/dts/imx6qdl-udoo.dtsi
> index 4161b7d..1f0b9f6 100644
> --- a/arch/arm/boot/dts/imx6qdl-udoo.dtsi
> +++ b/arch/arm/boot/dts/imx6qdl-udoo.dtsi
> @@ -274,7 +274,8 @@
>  	pinctrl-0 = <&pinctrl_usbh>;
>  	vbus-supply = <&reg_usb_h1_vbus>;
>  	clocks = <&clks IMX6QDL_CLK_CKO>;
> -	status = "okay";
> +	/* currently USB support causes a kernel hang. Disable it for now */
> +	status = "disabled";
>  };
>  
>  &usdhc3 {
> -- 
> 2.7.4
> 
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2018-02-22  3:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 12:34 [PATCH] ARM: dts: imx6qdl-udoo: Disable usbh1 to avoid kernel hang Fabio Estevam
2018-01-18 23:11 ` Maciej S. Szmigiero
     [not found]   ` <CAOcK=CNuopm0bq3s-jb2MJ0hHhLyYC1h3zquO__syN2=tU_nKQ@mail.gmail.com>
2018-01-18 23:25     ` Maciej S. Szmigiero
2018-01-18 23:50       ` Markus Rathgeb
2018-01-18 23:56         ` Maciej S. Szmigiero
2018-01-18 23:29   ` Markus Rathgeb
2018-01-19 12:03     ` Fabio Estevam
2018-01-19 11:59   ` Fabio Estevam
2018-01-19 13:38     ` Maciej S. Szmigiero
2018-01-20  9:14 ` Markus Rathgeb
2018-02-11 13:47   ` Markus Rathgeb
2018-02-11 13:58     ` Fabio Estevam
2018-02-11 19:21       ` Fabio Estevam
2018-02-11 23:23         ` Markus Rathgeb
2018-02-22  3: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=20180222034021.GE3217@dragon \
    --to=shawnguo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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