From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Tatyana Brokhman <tlinder@codeaurora.org>
Cc: gregkh@suse.de, linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [RFC/PATCH 0/4] UASP device driver
Date: Fri, 11 Feb 2011 14:47:03 -0800 [thread overview]
Message-ID: <20110211224703.GC9008@xanatos> (raw)
In-Reply-To: <1295595794-23194-1-git-send-email-tlinder@codeaurora.org>
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@codeaurora.org>
> 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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-11 22:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 7:43 [RFC/PATCH 0/4] UASP device driver Tatyana Brokhman
2011-01-21 15:23 ` Alan Stern
2011-01-23 5:53 ` Tanya Brokhman
2011-02-11 22:47 ` Sarah Sharp [this message]
2011-02-13 6:45 ` Tanya Brokhman
2011-02-14 18:31 ` Sarah Sharp
2011-02-21 6:48 ` UAS gadget driver & UAS host driver [was: Re: [RFC/PATCH 0/4] UASP device driver] Tanya Brokhman
2011-02-21 13:03 ` Matthew Wilcox
[not found] ` <20110221130307.GT3663-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2011-02-21 13:45 ` Tanya Brokhman
2011-02-21 14:58 ` Sarah Sharp
2011-02-21 15:35 ` Tanya Brokhman
2011-02-21 16:22 ` Sarah Sharp
2011-02-21 16:34 ` Alan Stern
2011-03-07 7:11 ` Tanya Brokhman
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=20110211224703.GC9008@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=gregkh@suse.de \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=tlinder@codeaurora.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).