Hi Sarah, Sorry. I just come back after two week vacation. Now I am working on three patches and will commit them ASAP. 1. xHCI-1.0-Endpoint-Not-Enabled-Error.patch 2. xHCI-1.0-Force-Stopped-Event-FSE.patch 3. xHCI-1.0-Incompatible-Device-Error.patch thanks, Alex -----Original Message----- From: linux-usb-owner@xxxxxxxxxxxxxxx [mailto:linux-usb-owner@xxxxxxxxxxxxxxx] On Behalf Of Sarah Sharp Sent: Wednesday, June 01, 2011 5:13 AM To: He, Alex Cc: Xu, Andiry; linux-usb@xxxxxxxxxxxxxxx Subject: Re: [RFC 7/9] xHCI 1.0: Endpoint Not Enabled Error Hi Alex, Any update for this patch? Sarah Sharp On Mon, May 09, 2011 at 09:19:58AM -0700, Sarah Sharp wrote: > On Fri, May 06, 2011 at 02:05:50PM +0800, Alex He wrote: > > No, I haven't seen this error code. The xhci_ring_ep_doorbell() has > > some condition limit for the endpoint. Shall we add the condition to > > limit the disable slot that we can throw away this patch? > > I would say do both. Add the condition check in > xhci_ring_ep_doorbell(), but also handle the error code in > handle_tx_event(). I don't think there's any race conditions in the > code that sets the endpoint state and the event handler, but I'd like to > leave this warning in just in case they crop up later. > > Sarah Sharp > -- > 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 -- 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 -- 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
