On Wed, Aug 14, 2013 at 11:22:39AM -0700, Greg KH wrote: > On Wed, Aug 14, 2013 at 03:59:31PM +0530, Tushar Behera wrote: > > Currently there is no other way to ensure that USB3503 chip is probed > > after the USB PHY has been initialized, hence the last resort. > Are you sure that deferred probing doesn't solve this issue? In order for deferred probing to help the device would need to acquire some resource from the parent USB controller once active, allowing it to defer when it fails to get that resource. Currently there's nothing there for that and it's not clear that's sane and sensible (it'd be more obvious for it to be a child of the USB controller since that's what it really is). We can't just treat it as a PHY (which is the obvious workaroud) since we do also need to use the built in PHY in the SoC.
Attachment:
signature.asc
Description: Digital signature
