[PATCH 0/2] Clarify DM_FLAG_PROBE_AFTER_BIND behaviour

[Michal Simek]

On 1/17/25 08:28, Caleb Connolly wrote:
> In Simons series reworking autoprobe[1], 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).
> 
> [1]: https://lore.kernel.org/u-boot/20241120153642.861633-1-sjg@chromium.org/
> 
> ---
> Caleb Connolly (2):
>        dm: clarify DM_FLAG_PROBE_AFTER_BIND behaviour
>        drivers: remove bogus DM_FLAG_PROBE_AFTER_BIND flags
> 
>   doc/develop/driver-model/design.rst | 6 ++++--
>   drivers/mailbox/zynqmp-ipi.c        | 1 -
>   drivers/watchdog/da9063-wdt.c       | 1 -
>   include/dm/device.h                 | 5 ++++-
>   4 files changed, 8 insertions(+), 5 deletions(-)
> ---
> base-commit: e3f716fa2d58aadf53928475ee7e88eb41cb8031
> 
> // Caleb (they/them)
> 

We can't se any issue on our HW when this is applied.

That's why
Acked-by: Michal Simek <michal.simek at amd.com>

Thanks,
Michal