On Fri, Nov 04, 2016 at 10:31:38AM +0200, Felipe Balbi wrote:
[snip]
> Sounds like VBUS dropping to me. Remember, MUSB is really anal about
> VBUS levels. If it drops enough for the PHY to report one of those 4
> VBUS levels, then MUSB just gives up.
>
> What we used to do back at Nokia was disable reporting of some of those
> VBUS levels at the PHY driver.
Well, I was getting these even without anything connected to musb:
[ 1526.594696] musb-hdrc musb-hdrc.0.auto: VBUS_ERROR in a_idle (90,
<VBusValid), retry #0, port1 00000104
[ 485.244781] musb-hdrc musb-hdrc.0.auto: VBUS_ERROR in a_idle (90,
<VBusValid), retry #0, port1 00000104
...and with the hub connected:
[ 562.803833] musb-hdrc musb-hdrc.0.auto: VBUS_ERROR in a_idle (90,
<VBusValid), retry #0, port1 00000507
[ 50.068664] musb-hdrc musb-hdrc.0.auto: VBUS_ERROR in a_idle (90,
<VBusValid), retry #0, port1 00000507
And indeed, after these errors musb gives up.
However these are gone with Tony's last patch. Bisecting now, approx 6
iterations left.
Best regards,
ladis
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
