Hi Tatyana, What have you been using on the host side to test your UAS gadget device? Is it the in-kernel UAS driver in 2.6.37, or perhaps the out-of-tree driver from Luben on git hub? Or have you been using a different driver? Thanks, Sarah Sharp On Fri, Jan 21, 2011 at 09:43:13AM +0200, Tatyana Brokhman wrote: > This patch series implements the UASP device driver. > The implementation is incomplete. We would like to receive comments > on the design. > > This patch series depends on "PATCH v4: usb: Add streams support to > the gadget framework" by Maya Erez <merez@xxxxxxxxxxxxxx> > http://marc.info/?l=linux-usb&m=129552394126050&w=2 > > TODO: Further testing > Implement TM IU handling > De-register the gadget if the main thread dies. > Add UASP-HS mode support. > > Tatyana Brokhman (4): > uasp: MS UAS Protocol implementation - Infrastructure > uasp: COMMAND IU handling infrastructure > uasp: COMMAND IU implementation > uasp: TASK MANAGEMENT IU handling infrastructure > > drivers/usb/gadget/f_mass_storage.c | 28 +- > drivers/usb/gadget/f_uasp.c | 2398 +++++++++++++++++++++++++++++++++++ > drivers/usb/gadget/f_uasp.h | 423 ++++++ > drivers/usb/gadget/mass_storage.c | 67 +- > drivers/usb/gadget/storage_common.c | 3 +- > drivers/usb/gadget/uasp_cmdiu.c | 1703 +++++++++++++++++++++++++ > drivers/usb/gadget/uasp_tmiu.c | 280 ++++ > 7 files changed, 4883 insertions(+), 19 deletions(-) > create mode 100644 drivers/usb/gadget/f_uasp.c > create mode 100644 drivers/usb/gadget/f_uasp.h > create mode 100644 drivers/usb/gadget/uasp_cmdiu.c > create mode 100644 drivers/usb/gadget/uasp_tmiu.c > > -- > Sent by a Consultant for Qualcomm Innovation Center, Inc. > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum > -- > To unsubscribe from this list: send the line "unsubscribe linux-usb" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
