linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Li Yang <leoli@freescale.com>
To: Scott Wood <scottwood@freescale.com>
Cc: greg@kroah.com, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org, dbrownell@users.sourceforge.net,
	linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] usb: add Freescale QE/CPM USB peripheral controller driver
Date: Fri, 29 Aug 2008 17:35:24 +0800	[thread overview]
Message-ID: <1220002524.30607.18.camel@Gundam> (raw)
In-Reply-To: <20080828163910.GA1185@ld0162-tx32.am.freescale.net>

On Thu, 2008-08-28 at 11:39 -0500, Scott Wood wrote:
> On Thu, Aug 28, 2008 at 05:43:33PM +0800, Li Yang wrote:
> > +config USB_GADGET_FSL_QE
> > +	boolean "Freescale QE/CPM USB Device Controller"
> > +	depends on FSL_SOC && (QUICC_ENGINE || CPM)
> > +	help
> > +	   Some of Freescale PowerPC processors have a Full Speed
> > +	   QE/CPM2 USB controller, which support device mode with 4
> > +	   programmable endpoints. This driver supports the
> > +	   controller in the MPC8360 and MPC8272, and should work with
> > +	   controllers having QE or CPM2, given minor tweaks.
> > +
> > +	   Say "y" to link the driver statically, or "m" to build a
> > +	   dynamically linked module called "fsl_qe_udc" and force all
> > +	   gadget drivers to also be dynamically linked.
> 
> How can you say "m" to something that is not a tristate?

Well, I copied these from other udc drivers.  Udc drivers can be
compiled as module, through the CONFIG_USB_GADGET option.  Though, the
description here is not accurate.

- Leo

  reply	other threads:[~2008-08-29  9:18 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28  9:43 [PATCH] usb: add Freescale QE/CPM USB peripheral controller driver Li Yang
2008-08-28 15:04 ` Arnd Bergmann
2008-08-28 17:22   ` Alan Stern
2008-08-28 17:53     ` Scott Wood
2008-08-28 20:16       ` Alan Stern
2008-08-28 22:27         ` Arnd Bergmann
2008-08-29 16:05           ` Alan Stern
2008-08-29 16:29             ` Arnd Bergmann
2008-08-29 17:19               ` Alan Stern
2008-08-29 17:38                 ` Arnd Bergmann
2008-08-29 21:22                   ` Alan Stern
2008-09-24 20:15           ` David Brownell
2008-08-29  8:57   ` Li Yang
2008-08-29  8:57     ` Arnd Bergmann
2008-09-24 20:10   ` David Brownell
2008-08-28 16:39 ` Scott Wood
2008-08-29  9:35   ` Li Yang [this message]
2008-09-01 13:52 ` Anton Vorontsov
2008-09-02  7:08   ` Li Yang
2008-09-01 16:34 ` Anton Vorontsov
2008-09-01 17:11 ` Anton Vorontsov
2008-09-02  7:35   ` Li Yang
2008-09-02  7:57     ` Joakim Tjernlund
2008-09-02  8:12       ` [PATCH] usb: add Freescale QE/CPM USB peripheral controllerdriver Li Yang-R58472
2008-09-02  8:15         ` Joakim Tjernlund
2008-09-24 20:28           ` David Brownell
2008-09-24 21:30             ` Joakim Tjernlund
2008-09-24 21:42               ` David Brownell
2008-09-24 20:26         ` David Brownell
  -- strict thread matches above, loose matches on Subject: below --
2008-08-06  7:16 [PATCH] usb: add Freescale QE/CPM USB peripheral controller driver Li Yang
2008-08-06 15:15 ` Anton Vorontsov
2008-08-06 15:47 ` Timur Tabi
2008-08-15 14:16 ` Anton Vorontsov

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=1220002524.30607.18.camel@Gundam \
    --to=leoli@freescale.com \
    --cc=dbrownell@users.sourceforge.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    /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).