From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: USB list <linux-usb@vger.kernel.org>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Mark Miesfeld <mmiesfeld@amcc.com>, Stefan Roese <sr@denx.de>
Subject: Re: [RFC][USB] powerpc: Workaround for the PPC440EPX USBH_23 errata
Date: Fri, 05 Sep 2008 11:35:08 +1000 [thread overview]
Message-ID: <1220578508.4879.94.camel@pasglop> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0809041737160.23455-100000@iolanthe.rowland.org>
> I assume that's the reason the suggested approach failed.
I think (hope) that Vitaly actually fixed that before trying it :-)
> 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.
I also find the CONFIG_PM approach not terribly reliable... too timing
sensitive, and it forces boards to add CONFIG_PM which is not
necessarily the nicest thing to do in embedded space.
Sounds better to me to clean up the initial patch to ensure it's not
going to introduce bloat for other platforms and use that, ie just
consider it as yet another HW errata.
Cheers,
Ben.
next prev parent reply other threads:[~2008-09-05 1:35 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 [this message]
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
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=1220578508.4879.94.camel@pasglop \
--to=benh@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 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).