[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87o98ajso9.fsf@linux.intel.com>
Date: Mon, 21 Jan 2019 10:55:50 +0200
From: Felipe Balbi <felipe.balbi@...ux.intel.com>
To: "Zengtao \(B\)" <prime.zeng@...ilicon.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"linux-usb\@vger.kernel.org" <linux-usb@...r.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>
Subject: RE: [PATCH] usb: dwc3: gadget: issue a stop command for ISOC endpoint
Hi,
"Zengtao (B)" <prime.zeng@...ilicon.com> writes:
>>-----Original Message-----
>>From: Felipe Balbi [mailto:felipe.balbi@...ux.intel.com]
>>Sent: Monday, January 21, 2019 4:17 PM
>>To: Zengtao (B) <prime.zeng@...ilicon.com>
>>Cc: Zengtao (B) <prime.zeng@...ilicon.com>; Greg Kroah-Hartman
>><gregkh@...uxfoundation.org>; linux-usb@...r.kernel.org;
>>linux-kernel@...r.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@...ilicon.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
Download attachment "signature.asc" of type "application/pgp-signature" (833 bytes)
Powered by blists - more mailing lists