Hi Rajendra,
On Wednesday 21 August 2013 12:43 PM, Rajendra Nayak wrote:
>> +void omap4_cminst_clkdm_force_sleep(u8 part, s16 inst, u16 cdoffs)
>> +{
>> + _clktrctrl_write(OMAP34XX_CLKSTCTRL_FORCE_SLEEP, part, inst, cdoffs);
>
> I guess this won't work on omap4/5 where some clockdomains do not support
> SW_SLEEP and only support HW_AUTO. We might need to have different clkdm
> operations for the different omap4 variants.
Yes, this has to be reworked using clockdomain flag to handle
appropriately the above scenario.
Regards
Afzal
>> static int omap4_clkdm_sleep(struct clockdomain *clkdm)
>> {
>> - omap4_cminst_clkdm_enable_hwsup(clkdm->prcm_partition,
>> - clkdm->cm_inst, clkdm->clkdm_offs);
>> + omap4_cminst_clkdm_force_sleep(clkdm->prcm_partition,
>> + clkdm->cm_inst, clkdm->clkdm_offs);
>> return 0;
>> }
>>
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
