On 01.03.2018 20:07, Alan Stern wrote:
On Thu, 1 Mar 2018, Mathias Nyman wrote:
Disabing Latency Tolerance Messaging before port reset is unnecessary.
LTM is automatically disabled at port reset.
If host can't communicate with the device the LTM message will fail, and
the hub driver will unnec
On Thu, 1 Mar 2018, Mathias Nyman wrote:
> Disabing Latency Tolerance Messaging before port reset is unnecessary.
> LTM is automatically disabled at port reset.
>
> If host can't communicate with the device the LTM message will fail, and
> the hub driver will unnecessarily do a logical disconnect
On 01.03.2018 13:56, Greg KH wrote:
On Thu, Mar 01, 2018 at 01:15:28PM +0200, Mathias Nyman wrote:
Disabing Latency Tolerance Messaging before port reset is unnecessary.
LTM is automatically disabled at port reset.
If host can't communicate with the device the LTM message will fail, and
the hub
On Thu, Mar 01, 2018 at 01:15:28PM +0200, Mathias Nyman wrote:
> Disabing Latency Tolerance Messaging before port reset is unnecessary.
> LTM is automatically disabled at port reset.
>
> If host can't communicate with the device the LTM message will fail, and
> the hub driver will unnecessarily do
Hello!
On 03/01/2018 02:15 PM, Mathias Nyman wrote:
> Disabing Latency Tolerance Messaging before port reset is unnecessary.
> LTM is automatically disabled at port reset.
>
> If host can't communicate with the device the LTM message will fail, and
> the hub driver will unnecessarily do a logica
Disabing Latency Tolerance Messaging before port reset is unnecessary.
LTM is automatically disabled at port reset.
If host can't communicate with the device the LTM message will fail, and
the hub driver will unnecessarily do a logical disconnect.
Broken communication is ofter the reason for a res
