Hi, On Thu, Jul 17, 2014 at 12:07:26PM +0530, Amit Virdi wrote: > >>can you send some logs of this patchset working ? What output should we > >>expect ? How to run it ? > >> > >>(sure, we could just read the source code and figure it out, but it's > >>good 'documentation' to put on the commit log) > >> > > > >In case the newly added tests pass, there's no log that the test passed > >(although kernel reports that it is going to execute the Test#). This > >has been the convention followed in the usbtest.c for all other tests as > >well. > > > >But surely, I can document how to execute the new tests and what to > >expect for failure scenarios. > > > > Let me know if you expect something like this in the commit logs: > > The two new tests added are > - Test 25: To verify Interrupt OUT transfer > - Test 26: To verify Interrupt IN transfer > > Since the default value of wMaxPacketSize is set as 1024, so interrupt IN > transfers must be specified with the size parameter = multiple of 1024. > Otherwise the default value (512) in the usbtest application fails the > transfer. See [RUN 4] for sample logs > > The application logs (usbtest) and corresponding kernel logs are as > following: > --- > [Run 1] > ./testusb -a -c 10 -s 2048 -t 26 -v 511 > Jul 17 10:31:13 dlhl1014 kernel: [72056.950910] usbtest 7-1:3.0: TEST 26: > read 2048 bytes 10 times > > [Run 2] > ./testusb -a -c 10 -s 1024 -t 25 -v 511 > Jul 17 10:31:29 dlhl1014 kernel: [72072.834853] usbtest 7-1:3.0: TEST 25: > write 1024 bytes 10 times > > [Run 3] > ./testusb -a -c 10 -s 1098 -t 25 -v 511 > Jul 17 10:31:39 dlhl1014 kernel: [72082.322219] usbtest 7-1:3.0: TEST 25: > write 1098 bytes 10 times > > [Run 4 - Failure case scenario] > ./testusb -a -t 26 > unknown speed /dev/bus/usb/007/004 0 > /dev/bus/usb/007/004 test 26 --> 75 (Value too large for defined data type) > > Jul 17 11:11:30 dlhl1014 kernel: [74473.347219] usbtest 7-1:3.0: TEST 26: > read 512 bytes 1000 times > Jul 17 11:11:30 dlhl1014 kernel: [74473.348959] usb 7-1: test26 failed, > iterations left 999, status -75 (not 0) that's good, thanks. But my tree is now closed for v3.17, once v3.17-rc1 is out I'll start queueing for v3.18. -- balbi
Attachment:
signature.asc
Description: Digital signature
