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
include/dm/device.h
+4 -1
View File
@@ -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)
/*