diff options
| author | Marek Vasut <marex@denx.de> | 2022-04-22 15:15:53 +0200 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2022-04-28 09:26:43 -0400 |
| commit | 9cc32bfa49d23a4d1bed9e6119255f2e78e20232 (patch) | |
| tree | 8b63349bf905b4b66764235a1361a79f3c2a2b20 /include | |
| parent | 8b2b125e95c44bb007b4573945f4aedb8a56222c (diff) | |
| download | u-boot-9cc32bfa49d23a4d1bed9e6119255f2e78e20232.zip u-boot-9cc32bfa49d23a4d1bed9e6119255f2e78e20232.tar.gz u-boot-9cc32bfa49d23a4d1bed9e6119255f2e78e20232.tar.bz2 | |
dm: core: Add DM_FLAG_PROBE_AFTER_BIND flag
Introduce DM_FLAG_PROBE_AFTER_BIND flag, which can be set by driver or
uclass in .bind(), to indicate such driver instance should be probe()d
once binding of all devices is complete.
This is useful in case the driver determines that hardware initialization
is mandatory on boot, and such initialization happens only in probe().
This also solves the inability to call device_probe() from .bind().
Signed-off-by: Marek Vasut <marex@denx.de>
Cc: Patrice Chotard <patrice.chotard@foss.st.com>
Cc: Patrick Delaunay <patrick.delaunay@foss.st.com>
Cc: Sean Anderson <seanga2@gmail.com>
Cc: Simon Glass <sjg@chromium.org>
Cc: Steven Lawrance <steven.lawrance@softathome.com>
Reviewed-by: Patrice Chotard <patrice.chotard@foss.st.com>
Tested-by: Patrice Chotard <patrice.chotard@foss.st.com>
Diffstat (limited to 'include')
| -rw-r--r-- | include/dm/device.h | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/include/dm/device.h b/include/dm/device.h index b474888..5bdb106 100644 --- a/include/dm/device.h +++ b/include/dm/device.h @@ -80,6 +80,9 @@ struct driver_info; */ #define DM_FLAG_VITAL (1 << 14) +/* Device must be probed after it was bound */ +#define DM_FLAG_PROBE_AFTER_BIND (1 << 15) + /* * One or multiple of these flags are passed to device_remove() so that * a selective device removal as specified by the remove-stage and the |