dm: do not set DM_FLAG_ACTIVATED twice
Currently, DM_FLAG_ACTIVATED is set twice; before calling uclass_pre_probe_device() and again before calling drv->probe(). It looks like Simon's intention is the first one. The DM_FLAG_ACTIVATED was moved twice, by commit02eeb1bbb1
(dm: core: Mark device as active before calling its probe() method), and then by commit206d4d2b4b
(dm: core: Mark device as active before calling uclass probe() methods). The first marking was added by the last move. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Acked-by: Simon Glass <sjg@chromium.org>
This commit is contained in:
parent
643e69021e
commit
1f5dd4700a
@ -284,7 +284,6 @@ int device_probe_child(struct udevice *dev, void *parent_priv)
|
||||
goto fail;
|
||||
}
|
||||
|
||||
dev->flags |= DM_FLAG_ACTIVATED;
|
||||
if (drv->probe) {
|
||||
ret = drv->probe(dev);
|
||||
if (ret) {
|
||||
|
Loading…
Reference in New Issue
Block a user