From: "Shimrit Malichi" <smalichi@codeaurora.org>
To: balbi@ti.com
Cc: "Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Shimrit Malichi" <smalichi@codeaurora.org>,
"Tatyana Brokhman" <tlinder@codeaurora.org>,
"USB GADGET/PERIPH..." <linux-usb@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
target-devel@vger.kernel.org
Subject: Re: [RFC] UASP on target
Date: Mon, 5 Dec 2011 04:10:50 -0800 (PST) [thread overview]
Message-ID: <9a0cf9e5dd108a8d17748c67afe45f9d.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <20111205091109.GG9900@legolas.emea.dhcp.ti.com>
> On Mon, Dec 05, 2011 at 09:55:13AM +0100, Sebastian Andrzej Siewior wrote:
>> On 12/05/2011 09:39 AM, Felipe Balbi wrote:
>> >Hi,
>> Hi,
>>
>> >On Mon, Dec 05, 2011 at 09:23:26AM +0100, Sebastian Andrzej Siewior
>> wrote:
>> >>* Sebastian Andrzej Siewior | 2011-12-05 09:20:47 [+0100]:
>> >>
>> >>>* Shimrit Malichi | 2011-12-04 21:53:09 [+0200]:
>> >>>
>> >>>>This patch implements the infrastructure for the UAS gadget driver.
>> >>>>The UAS gadget driver registers as a second configuration of the MS
>> >>>>gadet driver.
>> >>>hch said to use target framework and you haven't done so. This is
>> what I
>> >>>have so far. It is not yet complete. What I need to do is:
>> >>>- wire up command processing (currently here)
>> >>>- wire up data processing
>> >>>- check it works => post v1
>> >>>- wire up command tagging => v2
>> >>>- remove hard codings and fix whatever people complained about.
>> >
>> >This is much better, indeed, but the way it is now, it's only usable by
>> >the gadget framework because you have put the function driver on the
>> >transport layer. I wonder if there wouldn't be a simple way to split
>> the
>> >"SCSI Over USB" part in a more generic way which could be shared
>> between
>> >gadget side UASP and host side UASP drivers ?!? Maybe ?!?
>> >
>> >The drivers/target/uasp_*.c would really be just a transport layer and
>> >gadget/host drivers would make calls to that "library" ? Something like
>> >that ??
>>
>> There is very little code that is not host specific. For instance
>> uas_alloc_cmd_urb() is something that could be used on both side but
>> the host is boxing the command and I need to unbox it. So I don't see
>> how I could share things except for the defines.
>> Most of the things are usb specific. So UAS gets the commands from the
>> scsi framework, puts the usb layer around it and sends them.
>
> k, fair enough ;-) Just thought there'd be a better way to share this
> code with host side implementation. Nevermind then
>
> --
> balbi
>
Hi guys,
Thanks for your quick response.
We are glad to see that our initial implementation is being used and
gaining momentum.
We intend to learn and re-implement the UAS protocol using the target
framework, and continue our work started few months ago.
We hope to get your corporation in the future as well.
Thanks,
Shimrit
--
Consultant for Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next prev parent reply other threads:[~2011-12-05 12:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 19:53 [RFC/PATCH v4 1/3] uas: MS UAS Gadget driver - Infrastructure Shimrit Malichi
2011-12-05 8:20 ` [RFC] UASP on target (was: [RFC/PATCH v4 1/3] uas: MS UAS Gadget driver - Infrastructure) Sebastian Andrzej Siewior
2011-12-05 8:23 ` Sebastian Andrzej Siewior
2011-12-05 8:39 ` Felipe Balbi
2011-12-05 8:55 ` [RFC] UASP on target Sebastian Andrzej Siewior
2011-12-05 9:11 ` Felipe Balbi
2011-12-05 12:10 ` Shimrit Malichi [this message]
2011-12-05 12:14 ` Felipe Balbi
2011-12-05 16:10 ` [RFC] UASP on target (was: [RFC/PATCH v4 1/3] uas: MS UAS Gadget driver - Infrastructure) Alan Stern
2011-12-05 16:52 ` [RFC] UASP on target Sebastian Andrzej Siewior
2011-12-06 7:40 ` [RFC] UASP on target (was: [RFC/PATCH v4 1/3] uas: MS UAS Gadget driver - Infrastructure) Nicholas A. Bellinger
2011-12-06 9:19 ` [RFC] UASP on target Sebastian Andrzej Siewior
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=9a0cf9e5dd108a8d17748c67afe45f9d.squirrel@www.codeaurora.org \
--to=smalichi@codeaurora.org \
--cc=balbi@ti.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=target-devel@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
Powered by JetHome