All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
To: "Łukasz Pułka" <lukasz-u2dlg1C4t1k@public.gmane.org>
Cc: linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: PROBLEM: am3517 usb-ohci not working
Date: Fri, 7 Oct 2016 06:45:33 -0700	[thread overview]
Message-ID: <20161007134532.2c37bo4apnvuigkv@atomide.com> (raw)
In-Reply-To: <CALX2uoMnxQ00jiEbMEg4eOi8U0oxtQz1qip8RqcDF8Px2eKq0w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

* Łukasz Pułka <lukasz-u2dlg1C4t1k@public.gmane.org> [161007 03:14]:
> > Sounds like you're pretty close, in addition to the
> > pin muxing and PHY configuration, check also that you
> > have proper VBUS coming to the ports.
> 
> Thank you. It was hardware problem
> Finally I received the schematics of the PHY connection  from the board vendor.
> Suspend pin of PHY was pulled up and connected to gpio the expander.
> After forcing suspend pin to "0", USB HS works like a charm.

OK good to hear.

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2016-10-07 13:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05  6:36 PROBLEM: am3517 usb-ohci not working Łukasz Pułka
     [not found] ` <CALX2uoP-RN6SmEDOVcaBpJv+4kD2dY_iqxGjZu-5JFxdRAVfjA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-05 14:10   ` Tony Lindgren
     [not found]     ` <20161005141051.ywtf6ebakhhvrmst-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2016-10-07 10:13       ` Łukasz Pułka
     [not found]         ` <CALX2uoMnxQ00jiEbMEg4eOi8U0oxtQz1qip8RqcDF8Px2eKq0w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-07 13:45           ` Tony Lindgren [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=20161007134532.2c37bo4apnvuigkv@atomide.com \
    --to=tony-4v6ys6ai5vpbdgjk7y7tuq@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=lukasz-u2dlg1C4t1k@public.gmane.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 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.