Messages in this thread | | | From | Felipe Balbi <> | Subject | RE: [PATCH] usb: dwc3: gadget: issue a stop command for ISOC endpoint | Date | Mon, 21 Jan 2019 10:55:50 +0200 |
| |
Hi,
"Zengtao (B)" <prime.zeng@hisilicon.com> writes: >>-----Original Message----- >>From: Felipe Balbi [mailto:felipe.balbi@linux.intel.com] >>Sent: Monday, January 21, 2019 4:17 PM >>To: Zengtao (B) <prime.zeng@hisilicon.com> >>Cc: Zengtao (B) <prime.zeng@hisilicon.com>; Greg Kroah-Hartman >><gregkh@linuxfoundation.org>; linux-usb@vger.kernel.org; >>linux-kernel@vger.kernel.org >>Subject: Re: [PATCH] usb: dwc3: gadget: issue a stop command for ISOC >>endpoint >> >>* PGP Signed by an unknown key >> >> >>Hi, >> >>Zeng Tao <prime.zeng@hisilicon.com> writes: >>> For ISOC transfers, if there is no available data for a period, we >>> need to stop the transfer by issue a stop command, otherwise, all the >>> upcoming transfers will started by update transfer command, and will >>> be dropped with MISS ISOC errors. >> >>We, actually, have code to handle missed isoc errors now. Have you tested >>with that applied? Which kernel are you using? Can you share tracepoints >>captured with v5.0-rc3? >> > > Not v5.0-rc3, but I tested it based on 4.9 with backported dwc3 driver. And with > UVC application, it's very easy to reproduce it.
Ok, so it could be that you missed patches while backporting, right? How can I reproduce this? What do I need? Care to give detailed instructions?
-- balbi [unhandled content-type:application/pgp-signature]
| |