diff options
| author | Tom Rini <[email protected]> | 2025-03-30 09:10:57 -0600 |
|---|---|---|
| committer | Tom Rini <[email protected]> | 2025-03-30 09:11:07 -0600 |
| commit | f1895bc1e71c18fb872e2fec40ff2310d6b4a0bb (patch) | |
| tree | d1a588eb9f90acb777eff6be184f8dca36d504b2 /include/dm | |
| parent | 5ca70325b64f760bf4190f206a0e88dda495e3d2 (diff) | |
| parent | 44450434ea9f0f2e0d8ddfd853f4990c1719b4aa (diff) | |
Merge patch series "Clarify DM_FLAG_PROBE_AFTER_BIND behaviour"
Caleb Connolly <[email protected]> says:
In Simon's series reworking autoprobe, a discussion came up about
DM_FLAG_PROBE_AFTER_BIND, specifically that it wasn't very clear where
this flag should be used.
This series implements my suggestions made there to clarify the use of
this flag, and fixup the two driver which erroneously apply it to their
driver struct (this does nothing).
Link: https://lore.kernel.org/u-boot/[email protected]/
Link: https://lore.kernel.org/r/[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) /* |