Hi Zengtao,
On 12/16/2018 5:45 PM, Zengtao (B) wrote:
>> If it's a busy system, some times when we start an isoc transfer,
>> the framenumber get from the event buffer may be already elasped,
>> in this case, we will get all the packets dropped due to miss isoc.
>> And we turn into
rnel.org
>Subject: Re: [PATCH] usb: dwc3: gadget: fix miss isoc issue introduced by
>IRQ latency
>
>Hello!
>
>On 12/14/2018 07:32 PM, Zeng Tao wrote:
>
>> If it's a busy system, some times when we start an isoc transfer, the
>> framenumber get from the event buff
Thinh Nguyen
>
>Subject: Re: [PATCH] usb: dwc3: gadget: fix miss isoc issue introduced by
>IRQ latency
>
>Hi Zengtao,
>
>On 12/14/2018 3:24 AM, Felipe Balbi wrote:
>> Hi,
>>
>> "Zengtao (B)" writes:
>>>> -Original Message-
>>&
gt;> Cc: liangshengjun ; Zengtao (B)
>>> ; Greg Kroah-Hartman
>>> ; linux-usb@vger.kernel.org;
>>> linux-ker...@vger.kernel.org
>>> Subject: Re: [PATCH] usb: dwc3: gadget: fix miss isoc issue introduced by
>>> IRQ latency
>>>
>>> * PGP Si
el.org;
>>linux-ker...@vger.kernel.org
>>Subject: Re: [PATCH] usb: dwc3: gadget: fix miss isoc issue introduced by
>>IRQ latency
>>
>>* PGP Signed by an unknown key
>>
>>Zeng Tao writes:
>>
>>> If it's a busy system, some times when we
Hello!
On 12/14/2018 07:32 PM, Zeng Tao wrote:
> If it's a busy system, some times when we start an isoc transfer, the
> framenumber get from the event buffer may be already elasped, in this
Frame number? Else my spell checker trips. :-)
> case, we will get all the packets dropped due to mi
>-Original Message-
>From: Felipe Balbi [mailto:ba...@kernel.org]
>Sent: Friday, December 14, 2018 4:52 PM
>To: Zengtao (B)
>Cc: liangshengjun ; Zengtao (B)
>; Greg Kroah-Hartman
>; linux-usb@vger.kernel.org;
>linux-ker...@vger.kernel.org
>Subject: Re: [PATCH]
Zeng Tao writes:
> If it's a busy system, some times when we start an isoc transfer, the
> framenumber get from the event buffer may be already elasped, in this
> case, we will get all the packets dropped due to miss isoc. And we turn
> into transfer nothing, to fix this issue, we need to fix th
If it's a busy system, some times when we start an isoc transfer, the
framenumber get from the event buffer may be already elasped, in this
case, we will get all the packets dropped due to miss isoc. And we turn
into transfer nothing, to fix this issue, we need to fix the framenumber
to make sure
