| commit | 43f1069ef9af9a0b1fa1a1d6b49b2b05e1efc998 | |
| author | Mark Brown <broonie@opensource.wolfsonmicro.com> | |
| Tue, 3 Nov 2009 14:42:11 +0000 (3 14:42 +0000) | ||
| committer | Ben Dooks <ben-linux@fluff.org> | |
| Tue, 1 Dec 2009 01:35:38 +0000 (1 01:35 +0000) | ||
| tree | ac36835c0e6b0bfb0264fe7f62dfbf272179def0 | treesnapshot (tar.gz zip) |
| parent | 383af9c2586e0c51e27ed4f186a2f23f8e889054 | commitdiff |
ARM: S3C64XX: Separate out regulator and frequency latencies
Currently the transition latency reported by the S3C64xx cpufreq
driver includes both the time for the CPU to reclock itself and
the time for a regulator to change voltage. This means that if
a regulator is not in use then the transition latency reported
is excessively high.
In future the regulator API will be extended to report latencies
so the driver will be able to query the performance of a given
regulator.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: Ben Dooks <ben-linux@fluff.org>
Currently the transition latency reported by the S3C64xx cpufreq
driver includes both the time for the CPU to reclock itself and
the time for a regulator to change voltage. This means that if
a regulator is not in use then the transition latency reported
is excessively high.
In future the regulator API will be extended to report latencies
so the driver will be able to query the performance of a given
regulator.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: Ben Dooks <ben-linux@fluff.org>
| arch/arm/plat-s3c64xx/cpufreq.c | diffblobblamehistory |