On Tue, Aug 04, 2009 at 05:30:23PM -0500, Kanigeri, Hari wrote: > - obj->clk = clk_get(&pdev->dev, pdata->clk_name); > - if (IS_ERR(obj->clk)) > - goto err_clk; > + /* > + * FIX-ME: Replace with correct clk node when clk > + * framework is available > + */ > + if (!cpu_is_omap44xx()) { > + obj->clk = clk_get(&pdev->dev, pdata->clk_name); > + if (IS_ERR(obj->clk)) > + goto err_clk; > + } I've no visibility on when these are going to get resolved, and it's starting to concern me that there appears to be no progress on it, especially as we have more and more code being merged with these workarounds. It's getting towards the point where enough is enough and we need OMAP4 clk support in place, even if it is just a simple stop-gap implementation rather than all these horrible hacks spread through the code which one day will need to be found and removed. -- 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