Hi, On Thu Jan 8, 2026 at 3:13 PM CET, Mattijs Korpershoek wrote: > On Wed, Jan 07, 2026 at 16:15, Mattijs Korpershoek <[email protected]> > wrote: > >> Hi Markus, >> >> On Wed, Jan 07, 2026 at 15:01, Mattijs Korpershoek <[email protected]> >> wrote: >> >>> Hi, >>> >>> On Wed, 26 Nov 2025 21:31:06 +0100, Markus Schneider-Pargmann (TI.com) >>> wrote: >>>> musb currently uses a wrapper driver that binds on the parent device of >>>> the actual musb devices to manage the differentiation between gadget and >>>> host modes. However in the upstream devicetree this parent devicetree >>>> node can not be used to match the wrapper driver. >>>> >>>> To be able to probe the musb devices in host/gadget mode directly, this >>>> series introduces support for returning -ENODEV in bind functions >>>> resulting in iterating the remaining drivers potentially binding to >>>> other drivers that match the compatible. >>>> >>>> [...] >>> >>> Thanks, Applied to https://source.denx.de/u-boot/custodians/u-boot-dfu >>> (u-boot-dfu) >> >> It seems this series broke the CI when testing sandbox: >> https://source.denx.de/u-boot/custodians/u-boot-dfu/-/jobs/1349214 >> >> Can you have a look please? >> >> This can be reproduced locally using: >> >> $ ./test/py/test.py --bd sandbox --build -k test_bind >> [...] >> FAILED test/py/tests/test_bind.py::test_bind_unbind_with_node - >> AssertionError: assert 'Unable to bind. err:0' == '' >> FAILED test/py/tests/test_bind.py::test_bind_unbind_with_uclass - >> AssertionError: assert 2 == 1 > > We have discussed this on IRC (privately) and Markus has posted a v2 > that should address the CI failures here: > > https://lore.kernel.org/all/20260108-topic-musb-probing-v2026-01-v2-0-2a47c6e0e...@baylibre.com/
Yes, thank you Mattijs, sorry for not posting here. I missed the possible path of the drv argument being set and the driver not having an of_match being set. I fixed that in v2 and also added a few cleanups for the function. Best Markus
signature.asc
Description: PGP signature
