vhaudiquet/u-boot-krane
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

dm: clarify DM_FLAG_PROBE_AFTER_BIND behaviour

Browse Source 
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 <caleb.connolly@linaro.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
Acked-by: Michal Simek <michal.simek@amd.com>
This commit is contained in:
Caleb Connolly
2025-03-30 09:09:04 -06:00
committed by Tom Rini
parent c11dc783fb
commit 8a0e6212bb
2 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/develop/driver-model/design.rst
+4 -2
View File
@@ -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.