On Mon, Mar 19, 2012 at 11:33:21AM +0200, Tomi Valkeinen wrote: > But that's a bigger work item, so what I did in the series above is that > I changed platform_driver_register()s to platform_driver_probe()s. All > the DSS subdevices are present at boot time and are non-hotpluggable, so > I think that should work fine. platform_driver_probe() is just a wrapper around platform_driver_register() - the difference between the two is that _probe() will temporarily set the probe method in the passed driver structure, call platform_driver_register(), and then NULL the probe method out. So, merely changing platform_driver_register() for platform_driver_probe() won't solve the deadlock. I'm not sure what's caused this regression, as I can't see any DSS changes, nor core driver model changes which would account for this. Has something changed in hwmod to cause this? It is _very_ important that we discover what has caused this regression and prevent it going upstream until the problem is resolved. Until we know that, I suggest that _no_ OMAP changes go upstream during this merge window until we understand what's caused this. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
