On Thu, Apr 14, 2016 at 10:33:22PM +0100, Russell King - ARM Linux wrote: > The problem that's being addressed here is that there's no way at the > moment to know when the drivers on a different bus (namely the platform > bus) have probed and are providing the clock and power domain resources > necessary to be able to read these identifying values. > > I guess if you don't like a notifier, the other alternative is to > setup a delayed workqueue and have the workqueue repeatedly attempt > to register the devices until they all succeed. That's not > particularly nice, because we'd be wasting CPU cycles running > that workqueue for no reason until all the devices get registered. I like that idea, it handles the issue of this crazy hardware where it belongs, in that bus subsystem :) thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |