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 /doc/develop | |
| 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 'doc/develop')
| -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. |