From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: "Markus Schneider-Pargmann (TI.com)" <msp@baylibre.com>,
u-boot@lists.denx.de
Cc: Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>,
Marek Vasut <marex@denx.de>,
Mattijs Korpershoek <mkorpershoek@kernel.org>,
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>,
"Markus Schneider-Pargmann (TI.com)" <msp@baylibre.com>
Subject: Re: [PATCH 1/4] dm: core: Support multiple drivers with same compatibles
Date: Wed, 07 Jan 2026 14:16:59 +0100 [thread overview]
Message-ID: <871pk11s1g.fsf@kernel.org> (raw)
In-Reply-To: <20251126-topic-musb-probing-v2026-01-v1-1-ff8d8c487130@baylibre.com>
Hi Markus,
Thank you for the patch.
On Wed, Nov 26, 2025 at 21:31, "Markus Schneider-Pargmann (TI.com)" <msp@baylibre.com> wrote:
> Currently once a driver matched the compatible string of a device, other
> drivers are ignored. If the first matching driver returns -ENODEV, no
> other possibly matching drivers are iterated with that compatible of the
> device. Instead the next compatible in the list of compatibles is
> selected, assuming only one driver matches one compatible at a time.
>
> To be able to use the bind function to return -ENODEV and continue
> matching other drivers with the same compatible, move the for loop a bit
> to continue the for loop after -ENODEV was returned.
>
> This is required for ti-musb-host and ti-musb-peripheral which both
> match on the same device but differ based on the dr_mode DT property.
> Depending on this property, the driver is either UCLASS_USB or
> UCLASS_USB_GADGET_GENERIc. By checking the DT property in the bind
> function and returning -ENODEV the other driver can probe instead.
>
> Signed-off-by: Markus Schneider-Pargmann (TI.com) <msp@baylibre.com>
Reviewed-by: Mattijs Korpershoek <mkorpershoek@kernel.org>
> ---
> drivers/core/lists.c | 62 +++++++++++++++++++++++++++-------------------------
> 1 file changed, 32 insertions(+), 30 deletions(-)
>
next prev parent reply other threads:[~2026-01-07 13:17 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 [this message]
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
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=871pk11s1g.fsf@kernel.org \
--to=mkorpershoek@kernel.org \
--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=msp@baylibre.com \
--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