The device might have already been probed during the call to device_probe() on its parent device (e.g. PCI bridge devices). In its parent device's probe routine, it might probe all of its child devices via device_probe() thus the codes reenter device_probe_child(). To support code reentrancy, test these allocated memory against NULL to avoid memory leak, and return to the caller if dev->flags has DM_FLAG_ACTIVATED set after device_probe() returns, so that we don't mess up the device. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Acked-by: Simon Glass <sjg@chromium.org> |
||
|---|---|---|
| .. | ||
| Kconfig | ||
| Makefile | ||
| device-remove.c | ||
| device.c | ||
| devres.c | ||
| dump.c | ||
| lists.c | ||
| regmap.c | ||
| root.c | ||
| simple-bus.c | ||
| syscon-uclass.c | ||
| uclass.c | ||
| util.c | ||