On 30 August 2015 at 16:55, Simon Glass <s...@chromium.org> wrote:
> All devices should bind without error. But when they don't, they can cause
> driver model init to fail. A real situation where this can happen is when
> there is a missing uclass.
>
> Add a debug() call to dm_scan_fdt_node to make this easier to track.
>
> Signed-off-by: Simon Glass <s...@chromium.org>
> ---
>
> Changes in v5: None
> Changes in v4: None
> Changes in v3: None
> Changes in v2: None
>
>  drivers/core/root.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)

Applied to u-boot-rockchip.
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Reply via email to