Hi, 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. It also changes the address parsing of musb-ctrl to be able to parse relative addresses. Best Markus Signed-off-by: Markus Schneider-Pargmann (TI.com) <[email protected]> --- Markus Schneider-Pargmann (TI.com) (4): dm: core: Support multiple drivers with same compatibles test: dm: Add compatible multimatch test usb: musb-new: Relative ctrl_mod address parsing usb: musb-new: Add compatibles for ti,musb-am33xx arch/sandbox/dts/test.dts | 4 +++ drivers/core/lists.c | 62 ++++++++++++++++++++++-------------------- drivers/usb/musb-new/ti-musb.c | 36 +++++++++++++++++++++++- test/dm/core.c | 15 ++++++++++ test/dm/test-driver.c | 25 +++++++++++++++++ 5 files changed, 111 insertions(+), 31 deletions(-) --- base-commit: c5e6d2ab7eba68cbfb600cdc131c0c375ced2ec9 change-id: 20251125-topic-musb-probing-v2026-01-1343fff8176b Best regards, -- Markus Schneider-Pargmann (TI.com) <[email protected]>
