On 1 July 2014 12:07, Yegor Yefremov <yegorsli...@googlemail.com> wrote:
[..]
>
> What can be done with these error messages:
>
> of_get_named_gpiod_flags: can't parse gpios property of node
> '/ocp/usb@47400000/usb-phy@47401300[0]'
> 47401300.usb-phy supply vcc not found, using dummy regulator
> musb-hdrc musb-hdrc.0.auto: Failed to request rx1.
> musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517
> platform musb-hdrc.0.auto: Driver musb-hdrc requests probe deferral
> of_get_named_gpiod_flags: can't parse gpios property of node
> '/ocp/usb@47400000/usb-phy@47401b00[0]'
> 47401b00.usb-phy supply vcc not found, using dummy regulator
> musb-hdrc musb-hdrc.1.auto: Failed to request rx1.
> musb-hdrc musb-hdrc.1.auto: musb_init_controller failed with status -517
> platform musb-hdrc.1.auto: Driver musb-hdrc requests probe deferral
> couldn't find an available UDC
>

The above are typical deferal messages. Have you tried building
everything as a module or moving the DMA devicetree node so it's
probed earlier?

But I'm not sure it's related to the problem you are seeing.
-- 
Ezequiel García, VanguardiaSur
www.vanguardiasur.com.ar
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to