2 Aug
2013
2 Aug
'13
9:02 a.m.
On 2 August 2013 14:29, Tuukka Tikkanen tuukka.tikkanen@linaro.org wrote:
Like Mike said, the reason is the assumption that DVFS actions may want to sleep. While that may not be true for you, the governor you are working on might get used on a platform where these actions do sleep. Therefore, regardless of the actual situation, these functions are always assumed to need a non-interrupt context.
I have the same answer to this as what I wrote in my last mail.
BTW, The routine in question doesn't change frequency by itself. But the caller of this routine will change clk just after/before calling this routine.
And so, this routine doesn't need interrupts to be disabled.