The code at omap device level manages the constraints: storage,
tracking of requesters and dispatching to the low level
code (e.g. powerdomain for the wake-up latency constraints).
Tested on OMAP3 Beagleboard in RET/OFF using wake-up latency constraints
on MPU, CORE and PER.
Signed-off-by: Jean P
Jean Pihet writes:
> The code at omap device level manages the constraints: storage,
> tracking of requesters and dispatching to the low level
> code (e.g. powerdomain for the wake-up latency constraints).
>
> Tested on OMAP3 Beagleboard in RET/OFF using wake-up latency constraints
> on MPU, CORE
Kevin,
Thanks for reviewing!
All comments below fixed in the code. The updated series is coming asap.
More comments inlined below.
On Thu, Mar 17, 2011 at 9:36 PM, Kevin Hilman wrote:
> Jean Pihet writes:
>
>> The code at omap device level manages the constraints: storage,
>> tracking of reque
Jean Pihet writes:
[...]
>>> +exit_ok:
>>> + /* Find the strongest constraint for the given target */
>>> + ret = 0;
>>> + if (ascending) {
>>> + list_for_each_entry(user, &(constraints_list)->node_list,
>>> + node.plist.node_list) {
>>> +
