From: "Li Yang" <LeoLi@freescale.com>
To: "Kumar Gala" <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, gregkh@suse.de,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] [PATCH] Fix Freescale high-speed USB hostdependency
Date: Thu, 20 Jul 2006 22:03:52 +0800 [thread overview]
Message-ID: <a0bc9bf80607200703q7bcd4c31y4411b17a7a1cd5ee@mail.gmail.com> (raw)
In-Reply-To: <6DAE6213-B8D0-4226-9402-98B4F3FD907B@kernel.crashing.org>
On 7/20/06, Kumar Gala <galak@kernel.crashing.org> wrote:
>
> On Jul 20, 2006, at 8:36 AM, Li Yang wrote:
>
> > On 7/20/06, Kumar Gala <galak@kernel.crashing.org> wrote:
> >>
> >> On Jul 20, 2006, at 6:42 AM, Li Yang-r58472 wrote:
> >>
> >> > Another one in header file.
> >> >
> >> > ---
> >> > diff --git a/drivers/usb/host/ehci.h b/drivers/usb/host/ehci.h
> >> > index 679c1cd..8da2774 100644
> >> > --- a/drivers/usb/host/ehci.h
> >> > +++ b/drivers/usb/host/ehci.h
> >> > @@ -642,7 +642,7 @@ #endif
> >> >
> >> >
> >> > /
> >> >
> >> *--------------------------------------------------------------------
> >> -
> >> > -
> >> > ---*/
> >> >
> >> > -#ifdef CONFIG_PPC_83xx
> >> > +#ifdef CONFIG_MPC834x
> >> > /* Some Freescale processors have an erratum in which the TT
> >> > * port number in the queue head was 0..N-1 instead of 1..N.
> >> > */
> >>
> >> Do we really want to make this change. What harm is there in having
> >> the ehci support for MPC834x build on all 83xx processors? I can't
> >> imagine we are going to config in support for ehci on anything that
> >> is MPC834x at this point and if you do, your device tree isn't going
> >> to have nodes in it so the drivers not going to bind against
> >> anything.
> >>
> >
> > It's not very harmful. But it will cause some misunderstanding.
> > There were already some guys trying to use the 834x USB driver on 836x
> > and 832x. Anyway, it's a trivial patch. Please apply if it doesn't
> > cause much trouble.
>
> Is that more because the QE drivers aren't in the kernel tree?
>
> >> Finally, I got to believe Freescale's going to build some MPC83xx in
> >> the future with the high speed USB IP.
> >
> > I can't tell exactly. But it's not likely to integrate this IP into a
> > chip with QE/CPM support. As QE/CPM has already provided full speed
> > USB support, and the USB speed is not very important for Netcomm
> > processors.
>
> True, but not all 83xx are Netcomm processors.
83xx=PowerQUICC II Pro, IMHO.
I just give my 2 cents. It's up to you to decide as you are the maintainer. :)
>
> - k
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
next prev parent reply other threads:[~2006-07-20 14:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 11:58 [PATCH] Fix Freescale high-speed USB host dependency Li Yang
2006-07-14 13:51 ` Kumar Gala
2006-07-20 11:42 ` [linux-usb-devel] [PATCH] Fix Freescale high-speed USB hostdependency Li Yang-r58472
2006-07-20 12:59 ` Kumar Gala
2006-07-20 13:36 ` Li Yang
2006-07-20 13:42 ` Kumar Gala
2006-07-20 14:03 ` Li Yang [this message]
2006-08-01 15:38 ` David Brownell
2006-08-01 16:39 ` Kumar Gala
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=a0bc9bf80607200703q7bcd4c31y4411b17a7a1cd5ee@mail.gmail.com \
--to=leoli@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=gregkh@suse.de \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).