That goes back to Rafael's reply (and I agree):
"Also if the probe has already started, it may still return
-EPROBE_DEFER at any time in theory, so as a rule the dependency is
actually known to be satisfied when the probe has successfully
completed."
So waiting for the probe to finish is the right behavior/intentional
for fw_devlink.
But differs to how things actually work in the driver model. The
driver model does not care if a driver has finished probing, you can
use a resource as soon as it is registered. Hence this whole
problem/discussion.
Andrew