diff options
| author | Caleb Connolly <caleb.connolly@linaro.org> | 2025-01-17 08:28:56 +0100 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2025-03-30 09:09:04 -0600 |
| commit | 8a0e6212bb5ef547712e922a41555eb7d1aee1ab (patch) | |
| tree | 198116d296e1d91496953c51a928e4826783ee30 /test/py/tests/test_source.py | |
| parent | c11dc783fb4418393dd08d39ee01debfc2dea4d4 (diff) | |
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>
Diffstat (limited to 'test/py/tests/test_source.py')
0 files changed, 0 insertions, 0 deletions