common: Move autoprobe out to board init
authorSimon Glass <sjg@chromium.org>
Wed, 20 Nov 2024 15:36:41 +0000 (08:36 -0700)
committerTom Rini <trini@konsulko.com>
Tue, 14 Jan 2025 17:42:51 +0000 (11:42 -0600)
commit6995f2c8be901b5f3f4183ccc4a58c209e8bce52
tree92f8addda6ee3a888101a736c1fb7c5e5d5f719c
parent21dd873572a01d74bfdfceb7a30b056f8ccba187
common: Move autoprobe out to board init

Rather than doing autoprobe within the driver model code, move it out to
the board-init code. This makes it clear that it is a separate step from
binding devices.

For now this is always done twice, before and after relocation, but we
should discuss whether it might be possible to drop the post-relocation
probe.

For boards with SPL, the autoprobe is still done there as well.

Note that with this change, autoprobe happens after the
EVT_DM_POST_INIT_R/F events are sent, rather than before.

Link: https://lore.kernel.org/u-boot/20240626235717.272219-1-marex@denx.de/
Signed-off-by: Simon Glass <sjg@chromium.org>
common/board_f.c
common/board_r.c
common/spl/spl.c
doc/develop/driver-model/design.rst
drivers/core/root.c
include/dm/root.h