linux-toradex.git/include/linux/usb_gadget.h, branch v3.2.14

USB: move to

2007-10-12T21:55:31+00:00

Move  to , reducing
some of the clutter in the main include directory.

Signed-off-by: David Brownell 
Signed-off-by: Greg Kroah-Hartman

USB: gadget: gadget_is_{dualspeed,otg} predicates and cleanup

2007-10-12T21:55:03+00:00

This adds two small inlines to the gadget stack, which will
often evaluate to compile-time constants.  That can help
shrink object code and remove #ifdeffery.

 - gadget_is_dualspeed(), currently always a compile-time
   constant (depending on which controller is selected).

 - gadget_is_otg(), usually a compile time "false", but this
   is a runtime test if the platform enables OTG (since it's
   reasonable to populate boards with different USB sockets).

It also updates two peripheral controller drivers to use these:

 - fsl_usb2_udc, mostly OTG-related bugfixes:  non-OTG devices
   must follow the rules about drawing VBUS power, and OTG ones
   need to reject invalid SET_FEATURE requests.

 - omap_udc, just scrubbing a bit of #ifdeffery.

And also gadgetfs, which lost some #ifdefs and moved to a more
standard handling of DEBUG and VERBOSE_DEBUG.

The main benefits come from patches which will follow.

Signed-off-by: David Brownell 
Signed-off-by: Greg Kroah-Hartman

USB: usb_gadget.h whitespace fixes

2007-10-12T21:54:59+00:00

This just fixes some whitespace bugs in ,
mostly extraneous spaces where a single tab suffices.

Signed-off-by: David Brownell 
Signed-off-by: Greg Kroah-Hartman

usb gadget stack: remove usb_ep_*_buffer(), part 2

2007-07-12T23:34:42+00:00

This patch removes controller driver infrastructure which supported
the now-removed usb_ep_{alloc,free}_buffer() calls.

As can be seen, many of the implementations of this were broken to
various degrees.  Many didn't properly return dma-coherent mappings;
those which did so were necessarily ugly because of bogosity in the
underlying dma_free_coherent() calls ... which on many platforms
can't be called from the same contexts (notably in_irq) from which
their dma_alloc_coherent() sibling can be called.

The main potential downside of removing this is that gadget drivers
wouldn't have specific knowledge that the controller drivers have:
endpoints that aren't dma-capable don't need any dma mappings at all.

Signed-off-by: David Brownell 
Signed-off-by: Greg Kroah-Hartman

usb gadget stack: remove usb_ep_*_buffer(), part 1

2007-07-12T23:34:42+00:00

Remove usb_ep_{alloc,free}_buffer() calls, for small dma-coherent buffers.
This patch just removes the interface and its users; later patches will
remove controller driver support.

  - This interface is invariably not implemented correctly in the
    controller drivers (e.g. using dma pools, a mechanism which
    post-dates the interface by several years).

  - At this point no gadget driver really *needs* to use it.  In
    current kernels, any driver that needs such a mechanism could
    allocate a dma pool themselves.

Removing this interface is thus a simplification and improvement.

Note that the gmidi.c driver had a bug in this area; fixed.

Signed-off-by: David Brownell 
Signed-off-by: Greg Kroah-Hartman

[PATCH] USB: gadget section fixups

2006-07-12T23:03:24+00:00

Recent section changes broke gadget builds on some platforms.  This patch
is the best fix that's available until better section markings exist:

 - There's a lot of cleanup code that gets used in both init and exit paths;
   stop marking it as "__exit".

   (Best fix for this would be an "__init_or_exit" section marking, putting
   the cleanup in __init when __exit sections get discarded else in __exit.)

 - Stop marking the use-once probe routines as "__init" since references
   to those routines are not allowed from driver structures.  They're now
   marked "__devinit", which in practice is a net lose.

   (Best fix for this is likely to separate such use-once probe routines
   from the driver structure ... but in general, all busses that aren't
   hotpluggable will be forced to waste memory for all probe-only code.)

In general these broken section rules waste an average of two to four kBytes
per driver of code bloat ... because none of the relevant code can ever be
reused after module initialization.

Signed-off-by: David Brownell 
Signed-off-by: Greg Kroah-Hartman

[PATCH] USB: gadget driver section fixups

2006-03-20T22:49:58+00:00

This adds __init section annotations to gadget driver bind() routines to
remove calls from .text into .init sections (for endpoint autoconfig).
Likewise it adds __exit section annotations to their unbind() routines.

The specification of the gadget driver register/unregister functions is
updated to explicitly allow use of those sections.

Signed-off-by: David Brownell 
Signed-off-by: Greg Kroah-Hartman

[PATCH] gfp_t: drivers/usb

2005-10-28T15:16:49+00:00

Signed-off-by: Al Viro 
Signed-off-by: Linus Torvalds

[PATCH] USB: Fix kmalloc's flags type in USB

2005-07-12T18:52:56+00:00

Greg,

This patch fixes the kmalloc() flags argument type in USB
subsystem; hopefully all of its occurences. The patch was
made against patch-2.6.12-git2 from Jun 20.

Cleanup of flags for kmalloc() in USB subsystem.

Signed-off-by: Olav Kongas 
Signed-off-by: Greg Kroah-Hartman

[PATCH] USB: gadget driver updates (SETUP api change)

2005-06-27T21:43:53+00:00

This updates most of the gadget framework to expect SETUP packets use
USB byteorder (matching the annotation in  and usage
in the host side stack):

  - definition in 
  - gadget drivers:  Ethernet/RNDIS, serial/ACM, file_storage, gadgetfs.
  - dummy_hcd

It also includes some other similar changes as suggested by "sparse",
which was used to detect byteorder bugs.

Signed-off-by: David Brownell 
Signed-off-by: Greg Kroah-Hartman