diff options
| author | Caleb Connolly <[email protected]> | 2025-01-17 08:28:56 +0100 |
|---|---|---|
| committer | Tom Rini <[email protected]> | 2025-03-30 09:09:04 -0600 |
| commit | 8a0e6212bb5ef547712e922a41555eb7d1aee1ab (patch) | |
| tree | 198116d296e1d91496953c51a928e4826783ee30 /include/dm | |
| parent | c11dc783fb4418393dd08d39ee01debfc2dea4d4 (diff) | |
dm: clarify DM_FLAG_PROBE_AFTER_BIND behaviour
The DM_FLAG_PROBE_AFTER_BIND flag only makes sense on a per-device
basis, however recently added documentation as well as some confused
drivers imply that it might be added to a driver definition, this does
nothing.
Clarify the new documentation and expand on the comment by the
definition to point people in the right direction.
Signed-off-by: Caleb Connolly <[email protected]>
Reviewed-by: Simon Glass <[email protected]>
Acked-by: Michal Simek <[email protected]>
Diffstat (limited to 'include/dm')
| -rw-r--r-- | include/dm/device.h | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/include/dm/device.h b/include/dm/device.h index add67f9ec06..678cd83c271 100644 --- a/include/dm/device.h +++ b/include/dm/device.h @@ -81,7 +81,10 @@ struct driver_info; */ #define DM_FLAG_VITAL (1 << 14) -/* Device must be probed after it was bound */ +/* Device must be probed after it was bound. This flag is per-device and does + * nothing if set on a U_BOOT_DRIVER() definition. Apply it with + * dev_or_flags(dev, DM_FLAG_PROBE_AFTER_BIND) in the devices bind function. + */ #define DM_FLAG_PROBE_AFTER_BIND (1 << 15) /* |