public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org>
To: Alan Stern <stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org>
Cc: Greg KH
	<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
	USB list <linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: EHCI and MUSB do not discover devices without CONFIG_PM
Date: Tue, 28 Nov 2017 21:14:04 +0100	[thread overview]
Message-ID: <20171128201404.GA23974@lenoch> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1711281452520.1467-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>

On Tue, Nov 28, 2017 at 02:59:32PM -0500, Alan Stern wrote:
> On Tue, 28 Nov 2017, Ladislav Michl wrote:
> 
> > On Tue, Nov 28, 2017 at 01:09:45PM -0500, Alan Stern wrote:
> > > The EHCI debugging files require CONFIG_DYNAMIC_DEBUG to be enabled.  
> > > Oddly enough, the OHCI debugging files do not have the same 
> > > requirement.  I don't know the reason for this difference.
> > 
> > I see, thanks for suggestion.
> > 
> > USB cable unplugged:
> > $ cat /sys/kernel/debug/usb/ehci/48064800.ehci/registers 
> > bus platform, device 48064800.ehci
> > EHCI Host Controller
> > EHCI 1.00, rh state running
> > structural params 0x00001313
> > capability params 0x00000016
> > status 0000
> > command 0010005 (park)=0 ithresh=1 period=512 RUN
> > intrenable 37 IAA FATAL PCD ERR INT
> > uframe 0000
> > port:1 status 001000 0  ACK POWER sig=se0
> > port:2 status 001000 0  ACK POWER sig=se0
> > port:3 status 001000 0  ACK POWER sig=se0
> > irq normal 0 err 0 iaa 0 (lost 0)
> > complete 0 unlink 0
> > 
> > Plugged:
> > $ cat /sys/kernel/debug/usb/ehci/48064800.ehci/registers 
> > bus platform, device 48064800.ehci
> > EHCI Host Controller
> > EHCI 1.00, rh state running
> > structural params 0x00001313
> > capability params 0x00000016
> > status 0000
> > command 0010005 (park)=0 ithresh=1 period=512 RUN
> > intrenable 37 IAA FATAL PCD ERR INT
> > uframe 0000
> > port:1 status 001000 0  ACK POWER sig=se0
> > port:2 status 001000 0  ACK POWER sig=se0
> > port:3 status 001000 0  ACK POWER sig=se0
> > irq normal 0 err 0 iaa 0 (lost 0)
> > complete 0 unlink 0
> 
> So no change at all.  In particular, no change to the port statuses.  
> This suggests the hardware isn't configured properly; maybe a phy isn't
> detecting the new connection.
> 
> I don't know anything about the phy drivers, however.  You should bring 
> this to the attention of the maintainer for whichever phy is on your 
> board.

Thanks for suggestion, there's USB3326 ULPI PHY with nEN_USB_PWR connected
to TWL4030 LEDA output.

> By the way, the behavior when you plug in a device with CONFIG_PM=n
> should be just about the same as the behavior with CONFIG_PM=y when you
> plug in a _second_ device.  Have you tried doing that, say with two 
> flash drives?  (I'm assuming your board has more than one EHCI port 
> available.)

Unfortunately there's only one EHCI port, however your suggestions are
enough to start debugging.

Thank you,
	ladis
--
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:[~2017-11-28 20:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 22:08 EHCI and MUSB do not discover devices without CONFIG_PM Ladislav Michl
2017-11-28  7:33 ` Greg KH
     [not found]   ` <20171128073328.GF10757-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-11-28  8:57     ` Ladislav Michl
2017-11-28  9:03       ` Felipe Balbi
     [not found]         ` <87induzseh.fsf-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-11-28  9:42           ` Ladislav Michl
2017-11-28  9:30       ` Greg KH
     [not found]         ` <20171128093054.GA20720-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-11-28  9:39           ` Ladislav Michl
2017-11-28 14:11             ` Tony Lindgren
     [not found]               ` <20171128141131.GR28152-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-11-28 14:28                 ` Ladislav Michl
2017-11-28 14:39                   ` Tony Lindgren
     [not found]                     ` <20171128143913.GS28152-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-11-28 16:58                       ` Ladislav Michl
2017-11-28 17:16                         ` Tony Lindgren
2017-11-28 15:00     ` Alan Stern
     [not found]       ` <Pine.LNX.4.44L0.1711280956560.1467-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2017-11-28 16:05         ` Ladislav Michl
2017-11-28 18:09           ` Alan Stern
     [not found]             ` <Pine.LNX.4.44L0.1711281307250.1467-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2017-11-28 19:27               ` Ladislav Michl
2017-11-28 19:59                 ` Alan Stern
     [not found]                   ` <Pine.LNX.4.44L0.1711281452520.1467-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2017-11-28 20:14                     ` Ladislav Michl [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=20171128201404.GA23974@lenoch \
    --to=ladis-6z/3iimg2c8g8few9mqtra@public.gmane.org \
    --cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox