Hello, On Wednesday, July 27, 2011 2:25 PM Sangwook Lee wrote: > Func:samsung_pd_init should be postponed utill end of drivers > registeration because this activates runtime_suspend in advance. > > For example, > If PD's runtime_suspend is called, it will power down LCD0_CONF0. > Since this happens before s3cfb driver registers itself, > it makes s3cfb_probe hang up with both Origen and SMDK Nope. This is completely wrong. Power domain driver should be activated before any device drivers. If the driver hangs in probe() because the power domain has been suspended, then it is a bug in that driver. Each driver should call pm_runtime_get_sync() in it's probe if it supports runtime pm. If you delay registration of power domain driver, then how do you want to probe devices that belongs to power domains which has been disabled by bootloader? Our bootloader disables all power domains that are not needed at boot time. Best regards -- Marek Szyprowski Samsung Poland R&D Center -- 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