From: Felipe Balbi <balbi@ti.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Tatyana Brokhman <tlinder@codeaurora.org>,
greg@kroah.com, linux-usb@vger.kernel.org,
linux-arm-msm@vger.kernel.org, balbi@ti.com,
ablay@codeaurora.org, open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH/RFC 2/5] usb:dummy_hcd: connect/disconnect test support
Date: Thu, 16 Jun 2011 19:16:28 +0300 [thread overview]
Message-ID: <20110616161626.GV12230@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1106161101300.2204-100000@iolanthe.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
Hi,
On Thu, Jun 16, 2011 at 11:06:47AM -0400, Alan Stern wrote:
> On Thu, 16 Jun 2011, Tatyana Brokhman wrote:
>
> > This implementation adds a new proprietary device control requests (to be
> > handled by the dummy_hcd) that initiates a connect/disconnect sequence.
> > The bRequest value of the new control request is 0x52.
> > It is used by the user-space Unit testing application.
>
> This is not a bad idea. On the other hand, it is slightly peculiar --
> it you're testing with real UDC hardware, you would do the
> disconnect/reconnect sequence by hand (unplug and replug the USB
> cable), not in software.
actually, this is quite useful. Specially for the controllers which
_can_ do soft-connect by toggling data pullups. I would rather have
these sort of thing maybe in composite.c, so that we can build tests
with all gadget drivers/controllers, not only dummy_hcd.
That said, I think now it's not the time to fiddle too much with these
details right now. So best to keep this in dummy_hcd until we know the
test tools are actually good.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-06-16 16:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 13:31 [PATCH/RFC 1/5] usb:tools: usb unittests framework Tatyana Brokhman
2011-06-16 13:31 ` [PATCH/RFC 2/5] usb:dummy_hcd: connect/disconnect test support Tatyana Brokhman
2011-06-16 15:06 ` Alan Stern
2011-06-16 16:16 ` Felipe Balbi [this message]
2011-06-16 17:06 ` Alan Stern
2011-06-16 17:19 ` Alan Stern
2011-06-16 15:17 ` Alan Stern
2011-06-16 16:18 ` Felipe Balbi
2011-06-16 13:31 ` [PATCH/RFC 3/5] usb:g_zero: bulk in/out unittest support Tatyana Brokhman
2011-06-16 16:25 ` Felipe Balbi
2011-06-16 13:31 ` [PATCH/RFC 4/5] usb:dummy_hcd: Disable single-request fifo in dummy hcd Tatyana Brokhman
2011-06-16 15:09 ` Alan Stern
2011-06-16 13:31 ` [PATCH/RFC 5/5] usb: Add support for streams alloc/dealloc to devio.c Tatyana Brokhman
2011-06-16 15:20 ` Alan Stern
2011-06-16 16:28 ` Felipe Balbi
2011-06-16 18:21 ` Greg KH
2011-06-17 8:55 ` ablay
2011-06-17 14:35 ` Alan Stern
2011-06-30 17:45 ` Sarah Sharp
2011-06-30 18:39 ` William Gulland
2011-06-30 18:41 ` Tanya Brokhman
2011-07-19 9:12 ` Amit Blay
2011-07-19 9:18 ` Oliver Neukum
2011-07-19 10:07 ` Amit Blay
2011-07-19 10:26 ` Oliver Neukum
2011-07-19 10:36 ` Amit Blay
2011-07-27 6:21 ` Amit Blay
2011-08-17 7:06 ` Hans Petter Selasky
2011-08-18 22:47 ` Sarah Sharp
2011-08-21 10:18 ` Amit Blay
2011-08-22 7:58 ` Hans Petter Selasky
2011-08-22 7:56 ` Hans Petter Selasky
2011-08-22 16:41 ` Sarah Sharp
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=20110616161626.GV12230@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=ablay@codeaurora.org \
--cc=greg@kroah.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--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