On Mon, Jul 06, 2026 at 02:54:12PM +0200, Bartosz Golaszewski wrote: > The software node fw_devlink support already has its own kunit suite, but > that verifies the fwnode links in isolation. Add GPIO tests that prove > the ordering works in a real-life use-case: a GPIO consumer that > references its provider via a software node. > > The first suite registers the provider's software node, adds the consumer > device first and checks that fw_devlink defers its probe until the > provider has been added and bound. The second covers the fallback: > with the provider's software node not yet registered no supplier link is > created, so the consumer probes, devm_gpiod_get() returns -EPROBE_DEFER > and the consumer only binds once the provider shows up. > > While at it: the existing gpio_unbind_with_consumers() test keeps the > consumer bound while the provider goes away and then operates the orphaned > descriptor. With software nodes now being covered by fw_devlink that would > instead force-unbind the consumer along with the provider, so opt it out > by setting FWNODE_FLAG_LINKS_ADDED.
Acked-by: Andy Shevchenko <[email protected]> -- With Best Regards, Andy Shevchenko
