18 Oct, 2008

1 commit

  • The following patch introduces a new f_obex.c function driver.
    It allows userspace obex servers to use usb as transport layer
    for their messages.

    [ dbrownell@users.sourceforge.net: various fixes and cleanups ]

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

    Felipe Balbi
     

22 Jul, 2008

3 commits

  • Split out the generic serial support into a "function driver". This
    closely mimics the ACM support, but with a MUCH simpler control model.

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

    David Brownell
     
  • Split out CDC ACM parts of "gadget serial" to a "function driver".
    Some key structural differences from the previous ACM support, shared
    with with the generic serial function (next patch):

    - As a function driver, it can be combined with other functions.
    One gadget configuration could offer both serial and network
    links, as an example.

    - One serial port can be exposed in multiple configurations;
    the /dev/ttyGS0 node could be exposed regardless of which
    config the host selected.

    - One configuration can expose multiple serial ports, such as
    ttyGS0, ttyGS1, ttyGS2, and ttyGS3.

    This code should be a lot easier to understand than the previous
    all-in-one-big-file version of the driver.

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

    David Brownell
     
  • Add interfaces for composite gadget drivers, and
    basic implementation support behind it:

    - struct usb_function ... groups one or more interfaces into a function
    managed as one unit within a configuration, to which it's added by
    usb_add_function().

    - struct usb_configuration ... groups one or more such functions into
    a configuration managed as one unit by a driver, to which it's added
    by usb_add_config(). These operate at either high or full/low speeds
    and at a given bMaxPower.

    - struct usb_composite_driver ... groups one or more such configurations
    into a gadget driver, which may be registered or unregistered.

    - struct usb_composite_dev ... a usb_composite_driver manages this; it
    wraps the usb_gadget exposed by the controller driver.

    This also includes some basic kerneldoc.

    How to use it (the short version): provide a usb_composite_driver with a
    bind() that calls usb_add_config() for each of the needed configurations.
    The configurations in turn have bind() calls, which will usb_add_function()
    for each function required. Each function's bind() allocates resources
    needed to perform its tasks, like endpoints; sometimes configurations will
    allocate resources too.

    Separate patches will convert most gadget drivers to this infrastructure.

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

    David Brownell
     

17 Oct, 2007

1 commit

  • Fix two htmldocs build breaks, introduced by moving include/linux/usb_gadget.h to
    include/linux/usb/gadget.h and combining resume.c and suspend.c into main.c in
    drivers/base/power.

    Signed-off-by: Rob Landley
    Cc: "Randy.Dunlap"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Rob Landley
     

23 May, 2007

1 commit

  • This just removes some warnings generated by the Docbook tools when
    turning USB (host and peripheral side) kerneldoc into HTML; they're
    all about missing ID attributes.

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

    David Brownell
     

12 Feb, 2007

1 commit

  • Fix DocBook build. Regression was introduced by
    gregkh-usb-usb-linux-usb_ch9h-becomes-linux-usb-ch9h.patch

    Tested by `make htmldocs`.

    Signed-off-by: Don Mullis
    Cc: Greg KH
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Don Mullis
     

17 Apr, 2005

1 commit

  • Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds