linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: peter.chen@freescale.com (Peter Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: Enabling USBH1 on mx53qsb
Date: Thu, 25 Jul 2013 11:13:16 +0800	[thread overview]
Message-ID: <20130725031315.GA4489@nchen-desktop> (raw)
In-Reply-To: <CAOMZO5CAdxzn-3Xc2DZDYEXwsEznRrcqPbCbTDc5ieBkQkA8=g@mail.gmail.com>

On Wed, Jul 24, 2013 at 11:59:35PM -0300, Fabio Estevam wrote:
> Hi,
> 
> I am trying to get USBH1 port to work on mx53qsb (with Dialog pmic)
> with the following patch against linux-next-20130724:
> 
> --- a/arch/arm/boot/dts/imx53-qsb.dts
> +++ b/arch/arm/boot/dts/imx53-qsb.dts
> @@ -93,6 +93,15 @@
>                         regulator-max-microvolt = <3200000>;
>                         regulator-always-on;
>                 };
> +
> +               reg_usb_vbus: usb_vbus {
> +                       compatible = "regulator-fixed";
> +                       regulator-name = "usb_vbus";
> +                       regulator-min-microvolt = <5000000>;
> +                       regulator-max-microvolt = <5000000>;
> +                       gpio = <&gpio7 8 0>;
> +                       enable-active-high;
> +               };
>         };
> 
>         sound {
> @@ -145,6 +154,7 @@
>                                 MX53_PAD_EIM_DA12__GPIO3_12       0x80000000
>                                 MX53_PAD_EIM_DA13__GPIO3_13       0x80000000
>                                 MX53_PAD_PATA_DA_0__GPIO7_6       0x80000000
> +                               MX53_PAD_PATA_DA_2__GPIO7_8       0x80000000
>                                 MX53_PAD_GPIO_16__GPIO7_11        0x80000000
>                         >;
>                 };
> @@ -302,7 +312,8 @@
>  };
> 
>  &usbh1 {
> -       status = "okay";
> +       vbus-supply = <&reg_usb_vbus>;
> +       status = "okay";
>  };
> 
>  &usbotg {
> 
> 
> mx53qsb board has two USB host ports:
> 
> - The top port is USBH1
> - The bottom port is OTG (also shared with J3 connector)
> 
> After applying the above patch the OTG port does work, but the USBH1 does not.

Would you enable CONFIG_USB_DEBUG to see where is the problem?

> 
> However, if I access USBH1 within U-boot prior to launching the
> kernel, then I am able to use USBH1 in the kernel succesfully.

access host 1 at u-boot, what do you mean, only register access
or let host 1 work?

If it is really true, that means the kernel may omit some init steps
for host 1, but u-boot has.


-- 

Best Regards,
Peter Chen

  reply	other threads:[~2013-07-25  3:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25  2:59 Enabling USBH1 on mx53qsb Fabio Estevam
2013-07-25  3:13 ` Peter Chen [this message]
2013-07-25  3:28   ` Fabio Estevam
2013-07-25  3:37     ` Peter Chen
2013-07-25  3:44       ` Fabio Estevam
2013-07-25  3:57         ` Marek Vasut
2013-07-25 14:03 ` Arnaud Patard (Rtp)
2013-07-25 20:26   ` Fabio Estevam
2013-07-25 21:06     ` Fabio Estevam

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=20130725031315.GA4489@nchen-desktop \
    --to=peter.chen@freescale.com \
    --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;
as well as URLs for NNTP newsgroup(s).