From: Felipe Balbi <balbi@ti.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <greg@kroah.com>, Jack Pham <jackp@codeaurora.org>,
linux-usb@vger.kernel.org, Tim Sander <tim@krieglstein.org>,
Manu Gautam <mgautam@codeaurora.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [RFC/PATCH 2/2] usb: ehci: Add support for SINGLE_STEP_SET_FEATURE test of EHSET
Date: Thu, 25 Jul 2013 23:54:48 +0300 [thread overview]
Message-ID: <20130725205448.GA12343@radagast> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1307251539030.882-100000@iolanthe.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 2074 bytes --]
On Thu, Jul 25, 2013 at 03:44:20PM -0400, Alan Stern wrote:
> On Thu, 25 Jul 2013, Greg KH wrote:
>
> > On Tue, Jul 02, 2013 at 08:13:52PM -0700, Jack Pham wrote:
> > > From: Manu Gautam <mgautam@codeaurora.org>
> > >
> > > The USB Embedded High-speed Host Electrical Test (EHSET) defines the
> > > SINGLE_STEP_SET_FEATURE test as follows:
> > >
> > > 1) The host enumerates the test device with VID:0x1A0A, PID:0x0108
> > > 2) The host sends the SETUP stage of a GetDescriptor(Device)
> > > 3) The device ACKs the request
> > > 4) The host issues SOFs for 15 seconds allowing the test operator to
> > > raise the scope trigger just above the SOF voltage level
> > > 5) The host sends the IN packet
> > > 6) The device sends data in response, triggering the scope
> > > 7) The host sends an ACK in response to the data
> > >
> > > This patch adds additional handling to the EHCI hub driver and allows
> > > the EHSET driver to initiate this test mode by issuing a a SetFeature
> > > request to the root hub with a Test Selector value of 0x06. From there
> > > it mimics ehci_urb_enqueue() but separately submits QTDs for the
> > > SETUP and DATA/STATUS stages in order to insert a delay in between.
> > >
> > > Signed-off-by: Manu Gautam <mgautam@codeaurora.org>
> > > Signed-off-by: Jack Pham <jackp@codeaurora.org>
> >
> > Alan, any thoughts about this patch?
>
> Sorry, this slipped my mind.
>
> It looks okay. I haven't tested it yet (and it's so specialized that
> it probably will never receive very much testing). It is somewhat
> fragile, in that it copies part of usbcore into ehci-hcd; updates to
> the core will have to be mirrored in the driver.
>
> On the other hand, there's no real reason to reject it, and it could
> end up helping people who want to test new USB devices. So...
>
> Acked-by: Alan Stern <stern@rowland.harvard.edu>
Wait a minute, didn't we discuss a while back that these test features
should be built into usbcore so that we could have a usbcv clone for
linux ?
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-25 20:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1591113.JYQdTBbFW7@dabox>
2013-07-03 3:13 ` [PATCH 0/2] usb: Add support for EHSET Jack Pham
2013-07-03 3:13 ` [PATCH 1/2] usb: misc: EHSET Test Fixture device driver for host compliance Jack Pham
2013-07-03 3:13 ` [RFC/PATCH 2/2] usb: ehci: Add support for SINGLE_STEP_SET_FEATURE test of EHSET Jack Pham
2013-07-25 18:46 ` Greg KH
2013-07-25 19:44 ` Alan Stern
2013-07-25 20:54 ` Felipe Balbi [this message]
2013-07-25 21:33 ` Alan Stern
2013-08-09 13:41 ` Felipe Balbi
2013-08-09 14:37 ` Alan Stern
2013-08-09 14:44 ` Felipe Balbi
2013-08-09 15:04 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1308091053450.1405-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2013-08-12 17:53 ` Felipe Balbi
2013-08-12 18:52 ` Alan Stern
2013-08-13 15:32 ` Felipe Balbi
2013-08-13 16:47 ` Alan Stern
2013-08-13 23:05 ` Jack Pham
2013-08-14 14:10 ` Alan Stern
2013-08-14 17:05 ` Jack Pham
2013-07-25 22:09 ` Jack Pham
[not found] ` <20130725220925.GA28634-NjF/qFWh7jSrUKQWM4GlyCPyLMyjRtWwAL8bYrjMMd8@public.gmane.org>
2013-08-08 23:49 ` [PATCH " Jack Pham
2013-08-09 0:05 ` Greg KH
2013-08-09 2:12 ` Jack Pham
2013-08-09 2:32 ` Greg KH
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=20130725205448.GA12343@radagast \
--to=balbi@ti.com \
--cc=greg@kroah.com \
--cc=jackp@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mgautam@codeaurora.org \
--cc=stern@rowland.harvard.edu \
--cc=tim@krieglstein.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).