dm: clarify DM_FLAG_PROBE_AFTER_BIND behaviour
authorCaleb Connolly <caleb.connolly@linaro.org>
Fri, 17 Jan 2025 07:28:56 +0000 (08:28 +0100)
committerTom Rini <trini@konsulko.com>
Sun, 30 Mar 2025 15:09:04 +0000 (09:09 -0600)
commit8a0e6212bb5ef547712e922a41555eb7d1aee1ab
tree198116d296e1d91496953c51a928e4826783ee30
parentc11dc783fb4418393dd08d39ee01debfc2dea4d4
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 <caleb.connolly@linaro.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
Acked-by: Michal Simek <michal.simek@amd.com>
doc/develop/driver-model/design.rst
include/dm/device.h