Re: [RFT PATCH] xhci: handle no ping response error properly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Sep 21, 2015 at 03:41:19PM +0300, Mathias Nyman wrote:
> If a host fails to wake up a isochronous SuperSpeed device from U1/U2
> in time for a isoch transfer it will generate a "No ping response error"
> Host will then move to the next transfer descriptor.
> 
> Handle this case in the same way as missed service errors, tag the
> current TD as skipped and handle it on the next transfer event.

Thanks, I'll give it a shot later today. Note that it comes up rarely enough
these days (probably because my code is fast enough to deal with the data
flow) that it's not too easy to provoke the problem.

/* Steinar */
-- 
Homepage: http://www.sesse.net/
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux