dm: Provide better debugging when a device fails to bind
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 <sjg@chromium.org>
This commit is contained in:
parent
3346c87625
commit
bc7b2f431d
@ -162,8 +162,11 @@ int dm_scan_fdt_node(struct udevice *parent, const void *blob, int offset,
|
|||||||
continue;
|
continue;
|
||||||
}
|
}
|
||||||
err = lists_bind_fdt(parent, blob, offset, NULL);
|
err = lists_bind_fdt(parent, blob, offset, NULL);
|
||||||
if (err && !ret)
|
if (err && !ret) {
|
||||||
ret = err;
|
ret = err;
|
||||||
|
debug("%s: ret=%d\n", fdt_get_name(blob, offset, NULL),
|
||||||
|
ret);
|
||||||
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
if (ret)
|
if (ret)
|
||||||
|
Loading…
Reference in New Issue
Block a user