Hi
I am currently seeing a error with the designware driver on
Intel/Altera ARM Cortex A9 Cyclone SOC V Hardware. The USB PHY is a
TUSB1210 without a hw reset line connected. The error only occurs on
plugging in of the device in host mode. Once the USB device is
enumerated i have not seen any
Hi
Am Samstag, 29. Juni 2013, 15:39:52 schrieb Alan Stern:
On Fri, 28 Jun 2013, Jack Pham wrote:
Sorry to jump into this conversation just now but I saw this thread and
noticed the link to ehset.c. This file was authored by us at Qualcomm,
and had been added to the out-of-tree MSM port of
Hi Greg
snip
As for the referenced driver:
http://code.google.com/p/bricked/source/browse/drivers/usb/misc/ehset.
c
This is functionality which is not available within the kernel in a
way
that an external test device plugged triggers some test which in some
cases even
Hi Alan
I have just written a ehci testing driver which enables the testing modes
used for hw testing via a file in debugfs. This patch is for 3.4.47 not
any usb branch. But if this driver is ready for mainline i will be happy
to port it to whatever branch you wish.
It's not clear why
Hi Alan
I have just written a ehci testing driver which enables the testing
modes used for hw testing via a file in debugfs. This patch is for
3.4.47 not any usb branch. But if this driver is ready for mainline
i will be happy to port it to whatever branch you wish.
It's
Hi
I have just written a ehci testing driver which enables the testing modes used
for hw testing via a file in debugfs. This patch is for 3.4.47 not any usb
branch. But if this driver is ready for mainline i will be happy to port it to
whatever branch you wish.
The only problem with the patch
Hi
For testing purposes i would like to make my usb host connect only with
12MBit/s instead of 480Mbit/s. On a pc platform i would just unload the ehci
module but as the USB_EHCI_MXC depends on ehci this is not possible.
Are there any other options to disable hispeed mode. Like some magic in
Hi
I have some stange errors on a arm pcm043 with internal usb phy. The log is
attached at the end of the mail. It would be nice if someone could give me a
pointer whats going wrong?. It would also be nice to know where the status
flags which are output by the usb debug messages are
