Hi Afzal, On 05/07/2012 06:02 AM, Mohammed, Afzal wrote: > Hi Jon, > > On Fri, May 04, 2012 at 22:00:21, Hunter, Jon wrote: >>>>> + >>>>> + pdata->clk_prd = gpmc_get_fclk_period(); >>>> >>>> Does this need to be done here? May be this should be done in the probe >>>> function. You could store the handle to the main clk in the pdata. >>> >>> This is done so that migration of gpmc driver to the drivers folder >>> would be smooth, remember that this function will still live here. >> >> Sure, but why call this here? > > Clk_prd is a platform data passed to the driver, so platform code > updates it, where else can it be done ? The point is that you can pass what ever you like. You do not need to pass the frequency you can pass the clock handle instead. What happens it the clk_get() of the gpmc_l3_clk fails during the init? In fact if you migrate to runtime pm then we should not have the clk_get in the gpmc_init any more. Jon -- 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
