Hi, The packet is there on the USB bus, as well as the UDC driver. But it had not reached the gadget. Thanks, Chiranjeevi. On Wed, Aug 12, 2009 at 1:35 PM, Rajaram R<rajaram.officemail@xxxxxxxxx> wrote: > On Wed, Aug 12, 2009 at 3:59 PM, velempati > Chiranjeevi<velem.usb@xxxxxxxxx> wrote: >> Hi, >> >> I am currently working on the gadget framework. While performing the >> Mass storage CV test, >> around 50 % of the time the test passes and around 50 % of the time >> the test fails with the >> same code base. >> >> After doing a mass storage reset and after clearing the bulk-in & >> bulk-out endpoints, the host >> tries to issue the INQUIRY command, and the devices is not able to >> receive the command. >> >> Is the issue, with the latency involved with the kernel thread? When >> the test passes, how did the >> INQUIRY command get through with the same code base. >> >> Is there a way to decrease the latency of the kernel thread of the mass storage? > > AFAIK there is no timing requirement at class level??. When it fails, > till what level the USB packet reaches ? By level i mean ->can you see > the packet in : > > i) USB bus > ii) @ UDC driver > iii) @ Gadget Driver > .... > ..... >> >> >> Thanks, >> Chiranjeevi. >> -- >> 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 >> > -- 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
