| commit | 8d8a0dc87f38a260a00b3f3d7705d9ad0d467de9 | |
| author | Rajendra Nayak <rnayak@ti.com> | |
| Tue, 6 Oct 2009 13:20:13 +0000 (6 18:50 +0530) | ||
| committer | Kevin Hilman <khilman@deeprootsystems.com> | |
| Fri, 23 Oct 2009 18:21:53 +0000 (23 11:21 -0700) | ||
| tree | 96315840f4703c3c30b74965dc5673c3e4aec297 | treesnapshot (tar.gz zip) |
| parent | 3ddd27793bda5d7e0cb6d808c185bc0eea12542e | commitdiff |
OMAP3: SRF: Fix latency resource target value computations
The Shared resource framework currently considers the highest requested
level for a resource as the target level to be set. This works for OPP
and frequency resources as they are used to model performace based
constraints. However for latency based constraints/resources the least requested
level should be the one considered for the target level. This patch fixes
the issue by having an additional flag to identify the different types
of resources. Currently supported ones are Performace resources and
latency resources.
Signed-off-by: Rajendra Nayak <rnayak@ti.com>
The Shared resource framework currently considers the highest requested
level for a resource as the target level to be set. This works for OPP
and frequency resources as they are used to model performace based
constraints. However for latency based constraints/resources the least requested
level should be the one considered for the target level. This patch fixes
the issue by having an additional flag to identify the different types
of resources. Currently supported ones are Performace resources and
latency resources.
Signed-off-by: Rajendra Nayak <rnayak@ti.com>