Hi On 1/28/2012 2:03 AM, Sebastian Andrzej Siewior wrote: > This patch pushes two USB requests > - USB_REQ_SET_INTERFACE > - USB_REQ_SET_CONFIGURATION > > to be processed in process context. Both may perform some kind > initialisation which is better solved in process context than in atomic. > USB_REQ_SET_CONFIGURATION with config 0 also triggers disabling / > resetting which causes the dequeue of all requests. Having them in > process context will allow the UDC sleep and synchronize before it will > return. one question. What happens if host sends another setup packet while one of the above request is pending? Most of the controller drivers are nuking the endpoint and start processing the new packet. But the composite driver's processing is not canceled. I guess this can happen with the current "DELAYED_STATUS" implementation also. -- Sent by a consultant of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. -- 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
