On 07/07/2021 06:14, Bjorn Andersson wrote:
So you're going to rely on DT to create a role-switch link between the
dwc3 core driver and the qcom wrapper?
As I said the other day, this is just a hack to get around the fact that
of_platform_populate() may return before the dwc3 core has probed.
A beautiful hack though
Another such case can be seen in [1], where Wesley is patching the DT
node in runtime in order to pass a boolean parameter between the two
driver parts.
If we fix that we don't need these kinds of workarounds.
OK, I understand/agree
Lets look at changing the way dwc3-qcom launches dwc3-core and make it that
1. Probe deferral in dwc3-core either defers the dwc3-qcom code
2. Or that the dwc3-qcom code waits for dwc3-core
either way instead of avoiding the fact that dwc3-core can defer we
should make it that dwc3-qcom::probe() exits only when the dwc3-core is done
---
bod
