Thanks Alex. I appreciate you introducing me to Peter. Any help is appreciated. On the host (Wandboard iMX6q) the test app opens /dev/hidraw0 and write 64 bytes with report ID (1). The HID device has no Interrupt OUT ep, therefore uses control endpoint ep0 for the 64 bytes transfer to gadget (Wandboard iMX6q) using set_report. The setup phase is OK and the 64 bytes is written to gadget. However the chipidea interrupt (ci_irq()) and resulting udc interrupt (udc_irq()) is invoked. This indicates that the 64 bytes transaction is not completed over ep0 from host to gadget. **this issue is reproducible for all data transfers that aligns on 64 bytes** ~jayan On Fri, Jun 26, 2015 at 5:10 PM, Alexander Shishkin <alexander.shishkin@xxxxxxxxxxxxxxx> wrote: > Jayan John <jayanjohn79@xxxxxxxxx> writes: > >> I am developing a custom USB device on a iMX6q platform (Wandboard) >> Chipidea HDRC (highspeed dual role controller). The HID interface >> consists of a single Interrupt IN ep and ep0. It is required to send >> HID reports from Host to Gadget over ep0 (with set_report cmd on >> hidraw interface) in OUT direction. The size of each HID report is 64 >> bytes. >> >> The Chipidea HDRC is unable to receive/ process the 64 bytes of data >> over ep0 (OUT). The setup stage is fine. No UDC interrupt is raised by >> controller to indicate completion of transaction. The same data >> transfer works fine for <64 bytes (63, 63 etc) and >64 bytes (65, 66 >> etc) where the transfers are split as 64+n. Analyzer logs attached. >> >> 1. Is there an issue with Chipidea HDRC receiving wMaxPacketSize (i.e. >> 64 byte) aligned data transfers on ep0 in OUT direction? >> 2. Anything that needs to be configured/ added in descriptor or source >> to have completion interrupt hit on 64 bytes data transfer on ep0 OUT? > > Let's add Peter to CC as he's the maintainer for Chipidea now. How do > you generate this traffic? Are you using the zero gadget or some other > kind of test? > > Regards, > -- > Alex -- 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
