On Tue, 31 Aug 2010 10:53:36 +0530, kishon <a0393...@ti.com> wrote:
> Though driver shouldn't be using hwmod directly, there is no
> corresponding API in omap_device to do the same. So we are planning to
> store the omap_hwmod structure in platform_data during
> arch_initcall (in the callback to omap_hwmod_for_each_by_class). So
> whenever the
> AUTOIDLE bits need to be reset or set, we pass the stored
> omap_hwmod structure to this API. Currently, the functions that needs
> AUTOIDLE
> bit to be modified (omap_st_on, omap_st_off) resides in plat-omap.
couldn't your API instead be something like:
int omap_hwmod_set_autoidle(struct device *dev, u8 autoidle)
{
struct omap_hwmod *oh = dev_to_hwmod(dev);
if (!oh)
return -ENODEV;
[...]
return 0;
}
--
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
