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 /doc/develop/driver-model | |
| 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 'doc/develop/driver-model')
| -rw-r--r-- | doc/develop/driver-model/design.rst | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/develop/driver-model/design.rst b/doc/develop/driver-model/design.rst index 92f638a0204..30093737200 100644 --- a/doc/develop/driver-model/design.rst +++ b/doc/develop/driver-model/design.rst @@ -843,8 +843,10 @@ steps (see device_probe()): activated and 'known' by the uclass. For some platforms, certain devices must be probed to get the platform into -a working state. To help with this, drivers marked with DM_FLAG_PROBE_AFTER_BIND -will be probed immediately after all devices are bound. For now, this happens in +a working state. To help with this, devices marked with DM_FLAG_PROBE_AFTER_BIND +will be probed immediately after all devices are bound. This flag must be set +on the device in its ``bind()`` function with +``dev_or_flags(dev, DM_FLAG_PROBE_AFTER_BIND)``. For now, this happens in SPL, before relocation and after relocation. See the call to ``dm_autoprobe()`` for where this is done. |