ac218ced98
Currently, wait_for_device_probe api added before dwc3_probe is called in core_init which is suppose to ensure that in case the child is getting teared down, the userspace doesn't get to write UDC and do gadget_start. However, wait_for_device_probe api makes sure that the driver wait until all probes are completed. Ideally, it wouldn't be a problem but in cases of other driver's probe fails, usb would be affected here even though usb isn't at fault. Fix this by making a dummy-dependency on smmu node since the original intention of the patch was to make sure if smmu driver was probed successfully, then only proceed for child driver's probe. Change-Id: Id05797f8dcd26783e3c0eab4facf4f4672790fe6 Signed-off-by: Udipto Goswami <quic_ugoswami@quicinc.com> Signed-off-by: Ke Du <quic_kedu@quicinc.com>