On 13/9/19 10:58 pm, Mathias Nyman wrote:
> On 12.9.2019 17.49, Jan Schmidt wrote:
>> If an endpoint is encountered that returns USB3_LPM_DEVICE_INITIATED,
>> keep
>> checking further endpoints, as there might be periodic endpoints later
>> that return USB3_LPM_DISABLED due to shorter service inter
On 12.9.2019 17.49, Jan Schmidt wrote:
If an endpoint is encountered that returns USB3_LPM_DEVICE_INITIATED, keep
checking further endpoints, as there might be periodic endpoints later
that return USB3_LPM_DISABLED due to shorter service intervals.
Without this, the code can set too high a maxim
On Fri, 2019-09-13 at 00:49 +1000, Jan Schmidt wrote:
> If an endpoint is encountered that returns USB3_LPM_DEVICE_INITIATED, keep
> checking further endpoints, as there might be periodic endpoints later
> that return USB3_LPM_DISABLED due to shorter service intervals.
>
> Without this, the code c
If an endpoint is encountered that returns USB3_LPM_DEVICE_INITIATED, keep
checking further endpoints, as there might be periodic endpoints later
that return USB3_LPM_DISABLED due to shorter service intervals.
Without this, the code can set too high a maximum-exit-latency and
prevent the use of mu
