diff options
| author |   Rafael J. Wysocki <rjw@sisk.pl> | 2012-08-08 00:28:36 +0200 |
|---|---|---|
| committer | Rafael J. Wysocki <rjw@sisk.pl> | 2012-09-04 01:44:59 +0200 |
| commit | c37b7a7b3454ea6e6b457ab458c694fe4d81cf9e (patch) | |
| tree | a8e2eb9f26b6c3a0a39b0af58690355a3aef37c6 /tools/perf/scripts/python/syscall-counts-by-pid.py | |
| parent | ARM: shmobile: Allow device latencies to be specified directly (diff) | |
| download | linux-dev-c37b7a7b3454ea6e6b457ab458c694fe4d81cf9e.tar.xz linux-dev-c37b7a7b3454ea6e6b457ab458c694fe4d81cf9e.zip | |
ARM: shmobile: Specify device latencies for SH7372 devices directly
The results of adaptive latency computations in
GENPD_DEV_TIMED_CALLBACK() show that the start/stop and save/restore
state latencies of all devices on SH7372 I have tried are a little
below 250 us. Therefore, if the 250 us is used as the common initial
value of the latency fields in struct gpd_timing_data for all devices
on SH7372, the latency values will never have to change at run time
and there won't be any overhead related to re-computation of the
corresponding PM QoS data.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Magnus Damm <damm@opensource.se>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts-by-pid.py')
0 files changed, 0 insertions, 0 deletions