Re: [PATCH v2 3/3] usb: musb: da8xx: Only execute the OTG workaround when phy in OTG mode

2016-10-28 Thread Bin Liu
On Fri, Oct 28, 2016 at 12:11:21PM -0500, David Lechner wrote: > On 10/28/2016 07:39 AM, Alexandre Bailon wrote: > >On 10/28/2016 04:56 AM, David Lechner wrote: > >>On 10/26/2016 05:58 AM, Alexandre Bailon wrote: > >>>When the phy is forced in host mode, only the first hot plug and > >>>hot remove

Re: [PATCH v2 3/3] usb: musb: da8xx: Only execute the OTG workaround when phy in OTG mode

2016-10-28 Thread Bin Liu
On Fri, Oct 28, 2016 at 12:11:21PM -0500, David Lechner wrote: > On 10/28/2016 07:39 AM, Alexandre Bailon wrote: > >On 10/28/2016 04:56 AM, David Lechner wrote: > >>On 10/26/2016 05:58 AM, Alexandre Bailon wrote: > >>>When the phy is forced in host mode, only the first hot plug and > >>>hot remove

Re: [PATCH v2 3/3] usb: musb: da8xx: Only execute the OTG workaround when phy in OTG mode

2016-10-28 Thread David Lechner
On 10/28/2016 07:39 AM, Alexandre Bailon wrote: On 10/28/2016 04:56 AM, David Lechner wrote: On 10/26/2016 05:58 AM, Alexandre Bailon wrote: When the phy is forced in host mode, only the first hot plug and hot remove works. That is actually because the driver execute the OTG workaround,

Re: [PATCH v2 3/3] usb: musb: da8xx: Only execute the OTG workaround when phy in OTG mode

2016-10-28 Thread David Lechner
On 10/28/2016 07:39 AM, Alexandre Bailon wrote: On 10/28/2016 04:56 AM, David Lechner wrote: On 10/26/2016 05:58 AM, Alexandre Bailon wrote: When the phy is forced in host mode, only the first hot plug and hot remove works. That is actually because the driver execute the OTG workaround,

Re: [PATCH v2 3/3] usb: musb: da8xx: Only execute the OTG workaround when phy in OTG mode

2016-10-28 Thread Alexandre Bailon
On 10/28/2016 04:56 AM, David Lechner wrote: > On 10/26/2016 05:58 AM, Alexandre Bailon wrote: >> When the phy is forced in host mode, only the first hot plug and >> hot remove works. That is actually because the driver execute the >> OTG workaround, whereas it is not applicable in host or device

Re: [PATCH v2 3/3] usb: musb: da8xx: Only execute the OTG workaround when phy in OTG mode

2016-10-28 Thread Alexandre Bailon
On 10/28/2016 04:56 AM, David Lechner wrote: > On 10/26/2016 05:58 AM, Alexandre Bailon wrote: >> When the phy is forced in host mode, only the first hot plug and >> hot remove works. That is actually because the driver execute the >> OTG workaround, whereas it is not applicable in host or device

Re: [PATCH v2 3/3] usb: musb: da8xx: Only execute the OTG workaround when phy in OTG mode

2016-10-27 Thread David Lechner
On 10/26/2016 05:58 AM, Alexandre Bailon wrote: When the phy is forced in host mode, only the first hot plug and hot remove works. That is actually because the driver execute the OTG workaround, whereas it is not applicable in host or device mode. Indeed, to work correctly, the VBUS sense and

Re: [PATCH v2 3/3] usb: musb: da8xx: Only execute the OTG workaround when phy in OTG mode

2016-10-27 Thread David Lechner
On 10/26/2016 05:58 AM, Alexandre Bailon wrote: When the phy is forced in host mode, only the first hot plug and hot remove works. That is actually because the driver execute the OTG workaround, whereas it is not applicable in host or device mode. Indeed, to work correctly, the VBUS sense and

[PATCH v2 3/3] usb: musb: da8xx: Only execute the OTG workaround when phy in OTG mode

2016-10-26 Thread Alexandre Bailon
When the phy is forced in host mode, only the first hot plug and hot remove works. That is actually because the driver execute the OTG workaround, whereas it is not applicable in host or device mode. Indeed, to work correctly, the VBUS sense and session end comparator must be enabled, what is only

[PATCH v2 3/3] usb: musb: da8xx: Only execute the OTG workaround when phy in OTG mode

2016-10-26 Thread Alexandre Bailon
When the phy is forced in host mode, only the first hot plug and hot remove works. That is actually because the driver execute the OTG workaround, whereas it is not applicable in host or device mode. Indeed, to work correctly, the VBUS sense and session end comparator must be enabled, what is only