Re: [RFC] [PATCH] Debugfs support for EHCI testing modes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 28 Jun 2013, Tim Sander wrote:

> Alan userspace driver is a good replacement for the debugfs approach 
> (If working that is, what i am expecting at this point.). So my patch is not
> needed no discussion about that. This tool covers then:
> http://www.usb.org/developers/compliance/USB-IF_USB_2_0_Electrical_Test_Spec081005.pdf
> the steps needed on the device to manually (by commandline) to enable the testmodes.
> 
> But i am talking about this driver over here:
>  http://code.google.com/p/bricked/source/browse/drivers/usb/misc/ehset.c
> 
> There is a special usb debug device which can be switched to different "magic" usb id's which 
> are supposed to set the driver into a testing mode. So the idea is that you just plug in this special 
> and overpriced hardware and have your port in the configured testing mode on the device. The 
> detailed procedure is detailed over here:
> http://www.usb.org/developers/onthego/EHSET_v1.01.pdf‎;
> 
> So this is official functionality defined by the USB-IF. Keep in mind that an embedded linux device
> has no possibility to install the Intel USB Windows test suite and this is not needed with
> a *working* ehset driver in kernel.  Also this enables testing the ports without access to the
> commandline.  As i said this is a hardware driver which should IMHO live inside
> the kernel and should be implemented to fullfill the test procedures laid out by the USB-IF.

I just finished looking through the EHSET PDF file from www.usb.org.  
The description of the SINGLE_STEP_SET_FEATURE test appears to depend
on a hardware feature of the host controller that is not present in the
EHCI 1.0 spec -- maybe it was added as part of the OTG spec.  
Presumably the test device isn't meant to be used with a host
controller that doesn't support test mode 6 (which, BTW, seems to be
different from the test mode 6 description in your patch).

I also looked at the ehset driver on code.google.com.  It seems quite
reasonable.  If you or anyone else wants to submit that driver for
inclusion in the mainline kernel, go right ahead (but get permission
from the author first, of course).  There's no reason not to merge it.

Alan Stern

--
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




[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux