From: "Markus Schneider-Pargmann" <msp@baylibre.com>
To: "Mattijs Korpershoek" <mkorpershoek@kernel.org>,
"Markus Schneider-Pargmann (TI.com)" <msp@baylibre.com>
Cc: <u-boot@lists.denx.de>, "Simon Glass" <sjg@chromium.org>,
"Tom Rini" <trini@konsulko.com>, "Marek Vasut" <marex@denx.de>,
"Andrew Goodbody" <andrew.goodbody@linaro.org>,
"Kory Maincent" <kory.maincent@bootlin.com>,
"Svyatoslav Ryhel" <clamor95@gmail.com>,
"Christian Marangi" <ansuelsmth@gmail.com>,
"Dinesh Maniyam" <dinesh.maniyam@altera.com>,
"Heiko Schocher" <hs@nabladev.com>
Subject: Re: [PATCH 0/4] dm: core: Support same compatible in host/gadget musb drivers
Date: Thu, 08 Jan 2026 20:25:15 +0100 [thread overview]
Message-ID: <DFJGCWVN1KXA.1RO24AUIJQ1VM@baylibre.com> (raw)
In-Reply-To: <87ms2oyyxs.fsf@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2030 bytes --]
Hi,
On Thu Jan 8, 2026 at 3:13 PM CET, Mattijs Korpershoek wrote:
> On Wed, Jan 07, 2026 at 16:15, Mattijs Korpershoek <mkorpershoek@kernel.org> wrote:
>
>> Hi Markus,
>>
>> On Wed, Jan 07, 2026 at 15:01, Mattijs Korpershoek <mkorpershoek@kernel.org> 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-2a47c6e0e73a@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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 289 bytes --]
prev parent reply other threads:[~2026-01-08 20:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 20:31 [PATCH 0/4] dm: core: Support same compatible in host/gadget musb drivers Markus Schneider-Pargmann (TI.com)
2025-11-26 20:31 ` [PATCH 1/4] dm: core: Support multiple drivers with same compatibles Markus Schneider-Pargmann (TI.com)
2026-01-07 13:16 ` Mattijs Korpershoek
2025-11-26 20:31 ` [PATCH 2/4] test: dm: Add compatible multimatch test Markus Schneider-Pargmann (TI.com)
2026-01-07 13:35 ` Mattijs Korpershoek
2025-11-26 20:31 ` [PATCH 3/4] usb: musb-new: Relative ctrl_mod address parsing Markus Schneider-Pargmann (TI.com)
2026-01-07 13:44 ` Mattijs Korpershoek
2025-11-26 20:31 ` [PATCH 4/4] usb: musb-new: Add compatibles for ti,musb-am33xx Markus Schneider-Pargmann (TI.com)
2026-01-07 13:48 ` Mattijs Korpershoek
2026-01-07 14:01 ` [PATCH 0/4] dm: core: Support same compatible in host/gadget musb drivers Mattijs Korpershoek
2026-01-07 15:15 ` Mattijs Korpershoek
2026-01-08 14:13 ` Mattijs Korpershoek
2026-01-08 19:25 ` Markus Schneider-Pargmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DFJGCWVN1KXA.1RO24AUIJQ1VM@baylibre.com \
--to=msp@baylibre.com \
--cc=andrew.goodbody@linaro.org \
--cc=ansuelsmth@gmail.com \
--cc=clamor95@gmail.com \
--cc=dinesh.maniyam@altera.com \
--cc=hs@nabladev.com \
--cc=kory.maincent@bootlin.com \
--cc=marex@denx.de \
--cc=mkorpershoek@kernel.org \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox