linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Steven A. Falco" <sfalco@harris.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Stefan Roese <sr@denx.de>,
	linux-usb@vger.kernel.org, Mark Miesfeld <mmiesfeld@amcc.com>,
	"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [RFC][USB] powerpc: Workaround for the PPC440EPX USBH_23 errata
Date: Fri, 29 Aug 2008 09:25:37 -0400	[thread overview]
Message-ID: <48B7F8D1.3030500@harris.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0808281727090.4308-100000@iolanthe.rowland.org>

Alan Stern wrote:
> On Thu, 28 Aug 2008, Steven A. Falco wrote:
> 
>> Alan Stern wrote:
>>> Your original post mentioned that the 440EPx has only one USB 2.0 host
>>> port.  Then how can you use a keyboard and memory stick at the same
>>> time?  You'd have to plug them into a hub -- in which case only one
>>> controller would be needed, the one driving the hub.  The patch would 
>>> be unnecessary.
>> I have one of these processors on a Sequoia board.  What happens is that
>> if you build the kernel with both EHCI and OHCI support, then plug in
>> a modern USB memory stick, it initially tries EHCI, the driver fails, and
>> the whole thing falls back to OHCI.  So you wind up running at 12 Mbps.
>> The only way to make high speed work is to turn off the OHCI driver, and
>> then you cannot support slow devices with that kernel.
>>
>> So, hile you cannot plug two devices in at one time, you can plug in
>> different speed devices at different times, and my understanding is that
>> this patch will let that work seamlessly.
> 
> Is there some reason why it doesn't work already?  All the patch does
> is suspend the OHCI root hub when you plug in the memory stick -- but
> the root hub should already be suspended.
> 
> Unless the memory stick is already plugged in when the kernel boots.  
> In which case the root hub won't be suspended -- it won't suspend until 
> 1 second after ohci-hcd initializes the controller.  Is that the 
> scenario you're worried about?
Not sure about other users, but in my case, yes.  I was using a USB stick
as the root filesystem.  When the kernel first came up, it would try the
EHCI driver, which would fail.  Then the drive would be recognized by the
OHCI driver, but would only run at full (12 Mbps) speed rather than high
speed.

I've since gone to a directly attached CF card on the processor external
bus, and I'm not using USB anymore.  But I think the patch is still
desirable to work around the processor bug.

	Steve

> 
> Alan Stern
> 
> 

  parent reply	other threads:[~2008-08-29 13:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26 22:23 [RFC][USB] powerpc: Workaround for the PPC440EPX USBH_23 errata Vitaly Bordug
2008-08-27 14:36 ` Alan Stern
2008-08-28 19:32   ` Vitaly Bordug
2008-08-28 20:13     ` Alan Stern
2008-08-28 21:11       ` Steven A. Falco
2008-08-28 21:33         ` Alan Stern
2008-08-28 22:43           ` Benjamin Herrenschmidt
2008-08-29 15:26             ` Alan Stern
2008-08-29 18:20               ` Vitaly Bordug
2008-08-29 21:30                 ` Alan Stern
2008-09-04 20:48                   ` Vitaly Bordug
2008-09-04 21:40                     ` Alan Stern
2008-09-05  1:35                       ` Benjamin Herrenschmidt
2008-09-05 13:01                       ` Vitaly Bordug
2008-09-05 15:17                         ` Alan Stern
2008-09-06  9:02                           ` Vitaly Bordug
2008-08-29 13:25           ` Steven A. Falco [this message]
2008-08-29 17:56         ` Matthias Fuchs

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=48B7F8D1.3030500@harris.com \
    --to=sfalco@harris.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mmiesfeld@amcc.com \
    --cc=sr@denx.de \
    --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 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).