All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@ti.com>
To: Michael Trimarchi <michael@amarulasolutions.com>
Cc: USB list <linux-usb@vger.kernel.org>,
	Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: omap4 ehci sporadic resume issue
Date: Thu, 27 Jun 2013 16:59:38 +0300	[thread overview]
Message-ID: <51CC454A.1040104@ti.com> (raw)
In-Reply-To: <51CC2755.2030505@amarulasolutions.com>

Hi Michael,

On 06/27/2013 02:51 PM, Michael Trimarchi wrote:
> Hi
> 
> I'm working on omap4460 with two ulpi connected to (SMSC3320 -> HUB SMSC2514) or (TUSB1210 -> HUB SMSC2514). 
> The problem only happen when both port are used and after few suspend resume are triggered.
> If I use just one port there is no issue on suspend resume. I already covered all TI
> errata that I know and I'm working on TI kernel.
> 
> The problem is here
> 
> [   77.701934] ehci-omap ehci-omap.0: irq status a004 Async Recl PCD
> 
> Both ports change status from 001005 to 001009 (you have a log just after). 
> So from host point of view both hub connected are not working in HS mode. 
> After that the omap ehci has gone because the bus can not work in FS and LS and I can not recover from here.
> Status of transceivers are dumped and they are ok after resume.
> 
> Do you have any suggestion?

I'm not very sure but both ports suddenly changing state like that look like
a hardware issue. Also, it is strange that you can reproduce it only when two
ports are simultaneously in use. Unfortunately, I can't match your setup with 2 ULPI
ports.

I have a OMAP5 uEVM that uses 2 ports but it won't be identical to your setup as
they are on HSIC and not ULPI.

Did you try errata i693?

Also, are you suspending and resuming only the USB or the entire system?

cheers,
-roger

  reply	other threads:[~2013-06-27 13:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 11:51 omap4 ehci sporadic resume issue Michael Trimarchi
2013-06-27 13:59 ` Roger Quadros [this message]
     [not found]   ` <51CC454A.1040104-l0cyMroinI0@public.gmane.org>
2013-06-27 14:17     ` Michael Trimarchi
2013-06-27 14:49       ` Roger Quadros
2013-06-27 17:56         ` Michael Trimarchi
2013-06-27 18:59           ` Ruslan Bilovol
2013-06-27 19:24             ` Michael Trimarchi
2013-06-27 20:07               ` Ruslan Bilovol
2013-06-27 20:22                 ` Michael Trimarchi
2013-06-28 11:33                 ` Michael Trimarchi
2013-06-28 11:46                   ` Roger Quadros
     [not found]                     ` <51CD7783.8030907-l0cyMroinI0@public.gmane.org>
2013-06-28 12:26                       ` Michael Trimarchi
2013-06-28 12:55                         ` Roger Quadros
     [not found]                           ` <51CD87AC.6060107-l0cyMroinI0@public.gmane.org>
2013-06-28 14:52                             ` Michael Trimarchi
2013-06-28 16:47                       ` Michael Trimarchi
2013-07-02 14:42                         ` Roger Quadros
     [not found]                           ` <51D2E6DA.6030000-l0cyMroinI0@public.gmane.org>
2013-07-02 14:49                             ` Michael Trimarchi
2013-07-02 14:57                               ` Nishanth Menon
2013-07-02 15:03                               ` Roger Quadros
     [not found]                                 ` <51D2EBBB.8000504-l0cyMroinI0@public.gmane.org>
2013-07-04  8:53                                   ` Michael Trimarchi
2013-08-30 17:59                                     ` Michael Trimarchi
     [not found]                                       ` <CAOf5uwk9U8CHWywfopCt-H5BJmYyuXrwPvpwaqqP+5-3g_qYhQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-02  7:04                                         ` Roger Quadros
2013-06-28 19:42                     ` Michael Trimarchi

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=51CC454A.1040104@ti.com \
    --to=rogerq@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=michael@amarulasolutions.com \
    --cc=stern@rowland.harvard.edu \
    /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.