Hi, arch/arm/mach-tegra/cpu-tegra.c (as from nv-tegra.nvidia.com) contains a some strange comment:
493 /* FIXME: what's the actual transition time? */ 494 policy->cpuinfo.transition_latency = 300 * 1000; The trees on chromeos.org (both, kernel and kernel-next) have: 392 /* cpu clock change latency: ~400us */ 393 policy->cpuinfo.transition_latency = 400; because according to http://git.chromium.org/gitweb/?p=chromiumos/third_party/kernel.git;a=commitdiff;h=6a4debe346f5946f4fab14b413885896b7cde324 this improves latency of the GUI. Note that the comment said "us", while the cpu transition latency is measured in "ns", so 400 * 1000 would be right. So either the comment is wrong (should be 400ns) or the patch is wrong (which is unlikely, because it improved latency in the testcase). Can someone comment on this? Thanks Marc -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
