Re: [PATCH 2/2] drivers: usb: dwc2: remove 'force' parameter from kill_all_requests()

2015-01-28 Thread Robert Baldyga
On 01/27/2015 04:42 PM, Felipe Balbi wrote: > On Mon, Jan 05, 2015 at 10:31:35AM +0100, Robert Baldyga wrote: >> This patch fixes in simpler way the bug described in [1] and [2]. It >> looks like DWC2 is the only UDC driver that doesn't force usb requests >> to complete in ep_disable() function. Th

Re: [PATCH 2/2] drivers: usb: dwc2: remove 'force' parameter from kill_all_requests()

2015-01-28 Thread Felipe Balbi
On Wed, Jan 28, 2015 at 08:18:30AM +0100, Robert Baldyga wrote: > On 01/27/2015 04:42 PM, Felipe Balbi wrote: > > On Mon, Jan 05, 2015 at 10:31:35AM +0100, Robert Baldyga wrote: > >> This patch fixes in simpler way the bug described in [1] and [2]. It > >> looks like DWC2 is the only UDC driver tha

Re: [PATCH 2/2] drivers: usb: dwc2: remove 'force' parameter from kill_all_requests()

2015-01-27 Thread Felipe Balbi
On Mon, Jan 05, 2015 at 10:31:35AM +0100, Robert Baldyga wrote: > This patch fixes in simpler way the bug described in [1] and [2]. It > looks like DWC2 is the only UDC driver that doesn't force usb requests > to complete in ep_disable() function. This causes described problem, > because we have no

[PATCH 2/2] drivers: usb: dwc2: remove 'force' parameter from kill_all_requests()

2015-01-05 Thread Robert Baldyga
This patch fixes in simpler way the bug described in [1] and [2]. It looks like DWC2 is the only UDC driver that doesn't force usb requests to complete in ep_disable() function. This causes described problem, because we have no guarantee that all requests will be completed before unbind of usb func