Re: [PATCH] [musb_hdrc]: fix bug - EOVERFLOW failure when do usb gadget zero test t14
"Bryan Wu" <[email protected]> Mon, 30 Jun 2008 23:46:20 +0800
| Newsgroups | gmane.linux.usb.general,gmane.linux.usb.devel |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Jun 30, 2008 at 10:52 PM, Felipe Balbi <[email protected]> wrote: > On Mon, Jun 30, 2008 at 10:34:54PM +0800, ext Bryan Wu wrote: >> Yes, without the flush operation. It should always fail. >> -- >> root@adam:/home/test# sudo ./src/testusb -D /proc/bus/usb/005/007 -t14 >> -c 15000 -s 256 -v 1 >> unknown speed /proc/bus/usb/005/007 >> /proc/bus/usb/005/007 test 14 --> 75 (Value too large for defined data type) >> -- > > Cool, as soon as I get a analyzer, i'll also look at it. > >> I have a question about the driver: >> When does the driver ask MUSB to send out the last IN packet of the >> STATS tranfer? >> I think it is automatically controlled by hardware, right? When we >> write DATAEND to CSR0, >> it waits for host IN token and reply a ZERO length packet to host, right? > > As soon as I remember, yeah. Done by hw. > > There was a known issue when the CSR was 0x77ff (if I'm not wrong, will > look my mails and search for the right flakey csr), but we tested on > omap3 and it didn't seem to be affected. > Oh, is there any URL for this known issue? So happy to know we are in the same MAD USB (musb), -:)))) -Bryan -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html