On 7/22/26 11:43 PM, Carlo Caione wrote:
The MTU3 glue driver only supports the legacy U-Boot layout, where a
synthetic mediatek,ssusb child owns the gadget resources and dr_mode.
Upstream devicetrees instead place these properties directly on the
controller node. The gadget therefore cannot bind when U-Boot uses an
upstream devicetree.
Search the controller children for the legacy U-Boot-only node and use
the controller itself when none is present. This preserves compatibility
with existing U-Boot devicetrees while allowing the driver to consume the
upstream binding.
Can the U-Boot DTs be aligned with upstream DTs , and the driver fixed
instead ? Then this compatibility goo won't be necessary ?
