From: Vitaly Bordug <vitb@kernel.crashing.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: USB list <linux-usb@vger.kernel.org>,
Mark, "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Miesfeld <mmiesfeld@amcc.com>, Stefan Roese <sr@denx.de>
Subject: Re: [RFC][USB] powerpc: Workaround for the PPC440EPX USBH_23 errata
Date: Fri, 5 Sep 2008 17:01:35 +0400 [thread overview]
Message-ID: <20080905170135.07ccbc46@vitb-lp> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0809041737160.23455-100000@iolanthe.rowland.org>
В Thu, 4 Sep 2008 17:40:49 -0400 (EDT)
Alan Stern <stern@rowland.harvard.edu> пишет:
> On Fri, 5 Sep 2008, Vitaly Bordug wrote:
>
> > I've started looking this way. Sorry, but this approach is a little
> > bit fragile, and unreliable.
> >
> > First, it just did not work out in case of usb2 hub with memory
> > stick and keybord plugged - OHCI did not suspend, ehci is hosed and
> > we're happily using hi-speed device on full-speed:
>
> > Secondly, we may *not* rely on the fact, that OHCI will always have
> > the same suspend policy. Even kicking the code up to the shape when
> > it will automagically suspend in proper timing to get the HW issue
> > around, we cannot be sure that it will persist along kernel
> > lifecycle, and won't require concerned people to kick suspend
> > timings back to the working state subsequently each rc release.
> >
> > Thirdly, PM is disabled by Kconfig explicitly in case of 44x.
> > Reasoning is not clear at the moment, but I believe that isn't
> > there just in case.
>
> I assume that's the reason the suggested approach failed.
Oh geez. I may miss some small point, but dunno what made me appear
*that* dense. The kernel was properly rebuilt with Kconfig fixed and
_PM set.
>
> > > What to do when CONFIG_PM is off is a separate matter. Let's not
> > > worry about it for now -- especially since, as Matthias suggested,
> > > you can use a USB 2.0 hub.
> >
> > Not every hub will work (none of available did so far), and it is
> > often not an option for embedded device without rewiring.
>
> It's odd that your hubs don't work. What's wrong with them?
>
well, they do not have transaction translators then. Nothing really
wrong
> > As this touches powerpc stuff only, are there any objections to let
> > powerpc peolple consider if approach suggested earlier is
> > applicable or not?
>
> I don't mind doing that, provided the changes are cleaned up so that
> they don't affect people who aren't building kernels for 44x systems.
OK, thanks for review and comments...
--
Sincerely,
Vitaly
next prev parent reply other threads:[~2008-09-05 13:02 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 [this message]
2008-09-05 15:17 ` Alan Stern
2008-09-06 9:02 ` Vitaly Bordug
2008-08-29 13:25 ` Steven A. Falco
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=20080905170135.07ccbc46@vitb-lp \
--to=vitb@kernel.crashing.org \
--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 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.