{"push_id":770852046,"size":23,"distinct_size":23,"ref":"refs/heads/cm","head":"1c743f4834a8ddd5ca32245091f925a6564c46bc","before":"1839df80b3b77687a7986a0c23172a1746c7c524","commits":[{"sha":"e441299f92e29e455501e4af9da3f16edaa2c1eb","author":{"email":"ff359ca7f9aedbb05cd6aa3d17e7b3b3ad3b25c9@google.com","name":"Ruchi Kandoi"},"message":"cpufreq: Persist cpufreq time in state data across hotplug\n\nCpufreq time_in_state data for all CPUs is made persistent across\nhotplug and exposed to userspace via sysfs file\n/sys/devices/system/cpu/cpufreq/all_time_in_state\n\nChange-Id: I97cb5de24b6de16189bf8b5df9592d0a6e6ddf32\nSigned-off-by: Ruchi Kandoi <kandoiruchi@google.com>","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/e441299f92e29e455501e4af9da3f16edaa2c1eb"},{"sha":"dd5fa6f6c16410392c74f3b719233c19b804f4e8","author":{"email":"d36de655fd7d73924ee153ac87b341a5b17183d0@samsung.com","name":"Minsung Kim"},"message":"cpufreq: fix sleeping in atomic context when realloc freq_table for all_time_in_state\n\nCommit 40cf2f8 (cpufreq: Persist cpufreq time in state data across hotplug)\ncauses the following call trace to be spit on boot:\n\nBUG: sleeping function called from invalid context at mm/slub.c:936\nin_atomic(): 1, irqs_disabled(): 0, pid: 1, name: swapper/0\nCPU: 6 PID: 1 Comm: swapper/0 Not tainted 3.10.9-20140624.172707-eng-gd6c0f69-dirty #50\nBacktrace:\n[<c0012270>] (dump_backtrace+0x0/0x10c) from [<c001256c>] (show_stack+0x18/0x1c)\n r6:ffff1788 r5:c0c020c0 r4:e609c000 r3:00000000\n[<c0012554>] (show_stack+0x0/0x1c) from [<c07a2970>] (dump_stack+0x20/0x28)\n[<c07a2950>] (dump_stack+0x0/0x28) from [<c0057678>] (__might_sleep+0x104/0x120)\n[<c0057574>] (__might_sleep+0x0/0x120) from [<c00ff000>] (__kmalloc_track_caller+0x144/0x274)\n r6:00000000 r5:e609c000 r4:e6802140\n[<c00feebc>] (__kmalloc_track_caller+0x0/0x274) from [<c00da098>] (krealloc+0x58/0xb0)\n[<c00da040>] (krealloc+0x0/0xb0) from [<c050266c>] (cpufreq_allstats_create+0x120/0x204)\n r8:e4c4ff00 r7:c0d266b8 r6:0013d620 r5:e4c4e600 r4:00000001\nr3:e535d6d0\n[<c050254c>] (cpufreq_allstats_create+0x0/0x204) from [<c0502e38>] (cpufreq_stat_notifier_policy+0xb8/0xd0)\n[<c0502d80>] (cpufreq_stat_notifier_policy+0x0/0xd0) from [<c00517cc>] (notifier_call_chain+0x4c/0x8c)\n r5:00000000 r4:fffffffe\n[<c0051780>] (notifier_call_chain+0x0/0x8c) from [<c00519fc>] (__blocking_notifier_call_chain+0x50/0x68)\n r8:c0cd4d00 r7:00000002 r6:e609dd7c r5:ffffffff r4:c0d25a4c\nr3:ffffffff\n[<c00519ac>] (__blocking_notifier_call_chain+0x0/0x68) from [<c0051a34>] (blocking_notifier_call_chain+0x20/0x28)\n r7:c0e24f30 r6:00000000 r5:e53e1e00 r4:e609dd7c\n[<c0051a14>] (blocking_notifier_call_chain+0x0/0x28) from [<c0500fec>] (__cpufreq_set_policy+0xc0/0x1d0)\n[<c0500f2c>] (__cpufreq_set_policy+0x0/0x1d0) from [<c0501308>] (cpufreq_add_dev_interface+0x20c/0x270)\n r7:00000008 r6:00000000 r5:e53e1e00 r4:e53e1e58\n[<c05010fc>] (cpufreq_add_dev_interface+0x0/0x270) from [<c05016a8>] (cpufreq_add_dev+0x33c/0x420)\n[<c050136c>] (cpufreq_add_dev+0x0/0x420) from [<c03604a4>] (subsys_interface_register+0x80/0xbc)\n[<c0360424>] (subsys_interface_register+0x0/0xbc) from [<c050035c>] (cpufreq_register_driver+0x8c/0x194)\n\nChange-Id: If77a656d0ea60a8fc4083283d104509fa6c07f8f\nSigned-off-by: Minsung Kim <ms925.kim@samsung.com>","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/dd5fa6f6c16410392c74f3b719233c19b804f4e8"},{"sha":"4eb3ab5d1fff1e995cafcbabf8139943f7126610","author":{"email":"ce25c3cee4cc6c4c8acfc1680b3ed89cf644dba3@codeaurora.org","name":"Saravana Kannan"},"message":"cpufreq: Save user policy min/max instead of policy min/max during hotplug\n\nWhen a CPU is hotplugged off, various fields of the policy are saved so\nthat they can be restored when the CPU is hotplugged back in.\n\nThe existing code saves the policy min/max field during hotplug remove and\nrestores it into user policy min/max during hotplug add. This results in\nthe loss of the user policy min/max values across a hotplug remove/add.\n\nFix it by saving the user policy min/max instead of policy min/max during\nhotplug remove. During a hotplug add, after user policy min/max is\nrestored, the policy min/max is already recomputed. So, there's no risk of\ngoing beyound any limits imposed by the CPUFREQ_ADJUST/INCOMPATIBLE\nnotifiers.\n\nChange-Id: Ib8e09fa324c1f80f095c5754b5dcf2685e8e4a66\nSigned-off-by: Saravana Kannan <skannan@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/4eb3ab5d1fff1e995cafcbabf8139943f7126610"},{"sha":"399128a69aa7f667b26d4711283eec47eebb33c9","author":{"email":"bb05168246ed1a6b66d0e7b1ffb0c5e3707764ca@codeaurora.org","name":"Junjie Wu"},"message":"cpufreq: interactive: Round up timer_rate to match jiffy\n\nTimers are scheduled in unit of jiffies. Round up timer_rate so that\nit matches the actual sampling period.\n\nChange-Id: I47e666f835752528331f50b1e76784e6d67f8bcf\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/399128a69aa7f667b26d4711283eec47eebb33c9"},{"sha":"d7599359d5da8a7b4b0b082036785cbdcbdeb65a","author":{"email":"5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org","name":"Viresh Kumar"},"message":"cpufreq: interactive: Move definition of cpufreq_gov_interactive downwards\n\nThis moves definition of cpufreq_gov_interactive towards the bottom of file, so\nthat we don't have to add prototype of cpufreq_governor_interactive() in the\nbeginning of file.\n\nChange-Id: I04bd1004954eb36502c5cd7e35d3d7274cddaf95\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nGit-commit: e50d640cacfe61e69f1b4fa92fa0174c688e919c\nGit-Repo: https://android.googlesource.com/kernel/common.git\n[junjiew@codeaurora.org: Resolve merge conflicts]\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/d7599359d5da8a7b4b0b082036785cbdcbdeb65a"},{"sha":"f5a40b0cf0b358fb08205ef1fe3727b824927f68","author":{"email":"5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org","name":"Viresh Kumar"},"message":"cpufreq: Move get_cpu_idle_time() to cpufreq.c\n\nGovernors other than ondemand and conservative can also use\nget_cpu_idle_time() and they aren't required to compile\ncpufreq_governor.c. So, move these independent routines to\ncpufreq.c instead.\n\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nGit-commit: 72a4ce340a7ebf39e1c6fdc8f5feb4f974d6c635\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\n[junjiew@codeaurora.org: update non-upstream files]\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>\n\nChange-Id: I3227454599250011a19a752c962e3cacb1fb0301","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/f5a40b0cf0b358fb08205ef1fe3727b824927f68"},{"sha":"6ab6dba8c327cb8fbb77de1c59aadad5318b8500","author":{"email":"7f5bb03cf507c861269be561971108be8f37d832@chemlab.org","name":"Steve Kondik"},"message":"cpufreq: interactive: Squashed cleanup patches\n\nRevert \"cpufreq: interactive: Remove unnecessary cpu_online() check\"\n\nThis reverts commit 7b46e2e6d8a3c3c32706ee3c3c3b507d050bedfb.\n\nRevert \"cpufreq: interactive: Allow 1 ms error in above_hispeed_delay comparisons\"\n\nThis reverts commit ff6af80775231f1dfab8353d0b665718222218bf.\n\nCommit ff6af807 tries to avoid a corner case where frequency is stuck in\nhispeed_freq for one additional window. For example, if timer_rate is\n20ms, and go_hispeed_delay is 40ms, frequency might be stuck at\nhispeed_freq for 60ms due to imprecision in jiffies. Same problem can be\neasily solved by making go_hispeed_delay 1ms smaller instead of changing\nthe code.\n\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>\n\ncpufreq: interactive: Revert timer start modification\n\ncommit f8b276565ce95bd788af0fc8d060f92632590a40\n(cpufreq: Sync on thread migration optimizations)\nintroduced a change to cpufreq_interactive_timer_start() in order\nto reschedule the timer differently based on whether min or max\nis changed. A better way is to reschedule the timer only when\nnecessary.\n\nRevert timer start modification in preparation for the final fix.\n\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>\n\nRevert \"cpufreq: interactive: Optimize sync_freq implementation\"\n\nThis reverts commit 4da7f27d4dbd5bcfb8479467444f2cf198217933.\n\ncpufreq: interactive: Revert sync on thread migration optimizations\n\nCommit f8b276565ce95bd788af0fc8d060f92632590a40\n(cpufreq: Sync on thread migration optimizations) is no longer needed\nfor targets with synchronous CPUs.\n\nPart of that commit has already been reverted in\na913b3afcaa55356f5f793ae895312c8ae7e1f71\n(cpufreq: interactive: Revert timer start modification)\n\nThis commit reverts the remaining changes.\n\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>\n\ncpufreq: interactive: Revert sync freq feature\n\nSync freq feature is not valid for a HMP system with clusters.\n\nThis commit reverts commit f3d1980b4db4c20f21acaed59cc511c2df84cec2\n(cpufreq: interactive: sync freq feature for interactive governor)\n\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>\n\ncpufreq: interactive: Remove sampling_down_factor\n\nRemove sampling_down_factor feature.\n\nThis commit revert d094d23694edf41fee50ebc544795d6116451643\n(cpufreq: interactive: Add a sampling_down_factor for max frequencies)\nand subsequent modifications related to sampling down factor.\n\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>\n\nConflicts:\n\tdrivers/cpufreq/cpufreq_interactive.c\n\nChange-Id: I9e5fd451e7eaefe8ef7775365cc5a4527d37188f","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/6ab6dba8c327cb8fbb77de1c59aadad5318b8500"},{"sha":"0cc1734bb77e24a4d24dd30961f67b9e013edc20","author":{"email":"bb05168246ed1a6b66d0e7b1ffb0c5e3707764ca@codeaurora.org","name":"Junjie Wu"},"message":"cpufreq: interactive: Align timer windows for all CPUs\n\nIt's more advantageous to evaluate all CPUs at same time so that\ninteractive governor gets a complete picture of the load on\neach CPU at a specific time. It could also reduce number of speed\nchanges made if there are many CPUs controlled by same policy. In\naddition, waking up all CPUs at same time would allow the cluster\nto go into a deeper sleep state when it's idle.\n\nChange-Id: I6915050c5339ef1af106eb906ebe4b7c618061e2\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/0cc1734bb77e24a4d24dd30961f67b9e013edc20"},{"sha":"e1769f43abdfb4d2e24fe7d4f666452c86416539","author":{"email":"bb05168246ed1a6b66d0e7b1ffb0c5e3707764ca@codeaurora.org","name":"Junjie Wu"},"message":"cpufreq: interactive: Reset last evaluated jiffy in idle callback\n\nWhen CPU has been busy for a long time, last evaluated jiffy will be\nquite behind because the timer would have been canceled. We don't want\nto schedule a timer to fire in the past as load will always be 100%.\n\nReset last evaluated jiffy so that timer will be scheduled for the\nnext window.\n\nChange-Id: Ie25e65eab1f16acdeda267987ca605d653f1f32a\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/e1769f43abdfb4d2e24fe7d4f666452c86416539"},{"sha":"03d7b3c49886ec99aa4c480306d2f2bc43602ae3","author":{"email":"bb05168246ed1a6b66d0e7b1ffb0c5e3707764ca@codeaurora.org","name":"Junjie Wu"},"message":"cpufreq: interactive: Use del_timer/add_timer_on to rearm timers\n\nReplace mod_timer_pinned() with del_timer(), add_timer_on().\nmod_timer_pinned() always adds timer onto current CPU. Interactive\ngovernor expects each CPU's timers to be running on the same CPU.\nIf cpufreq_interactive_timer_resched() is called from another CPU,\nthe timer will be armed on the wrong CPU.\n\nReplacing mod_timer_pinned() with del_timer() and add_timer_on()\nguarantees timers are still run on the right CPU even if another\nCPU reschedules the timer. This would provide more flexibility\nfor future changes.\n\nChange-Id: I3a10be37632afc0ea4e0cc9c86323b9783b216b1\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/03d7b3c49886ec99aa4c480306d2f2bc43602ae3"},{"sha":"1d23962f06d7b4eb3f35df452f8a8796c8da4124","author":{"email":"bb05168246ed1a6b66d0e7b1ffb0c5e3707764ca@codeaurora.org","name":"Junjie Wu"},"message":"cpufreq: interactive: Add max_freq_hysteresis feature\n\nPreviously known as sampling down factor, max_freq_hysteresis\nextends the period that interactive governor will stay at policy->max.\nThis feature is to accomodate short idle periods in an otherwise very\nintensive workload.\n\nWhen the feature is enabled, it ensures that once a CPU goes to max\nfrequency, it doesn't reduce the frequency for max_freq_hysteresis\nmicroseconds from the time it first goes to idle.\n\nChange-Id: Ia54985cb554f63f8c22d0b554a0a0f2ed2be038f\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/1d23962f06d7b4eb3f35df452f8a8796c8da4124"},{"sha":"d1e778de671b545d2521de2a20f34ba4e0722c9e","author":{"email":"ce25c3cee4cc6c4c8acfc1680b3ed89cf644dba3@codeaurora.org","name":"Saravana Kannan"},"message":"cpufreq: interactive: Exercise hispeed settings at a policy level\n\nIf a heavy task migrates between otherwise idle CPUs in a policy during\nevery sample window, the above hispeed delay window for the CPUs would get\nrestarted for every sample window. Due to the continuous restart of above\nhispeed delay window, none of the CPUs would ever pick a target frequency\nhigher than hispeed frequency. This causes the policy's frequency to be\nstuck at hispeed freq even if the load justifies a higher frequency.\n\nTo fix this, the above high speed delay window is restarted only when the\npolicy frequency changes. This ensures that tasks migrating between CPUs in\na policy are handled correctly.\n\nAlso, the hispeed load/frequency heuristic is only necessary when the\ninformation is insufficient to determine if the load on the CPU needs at\nleast hispeed frequency. When the policy frequency is already at or above\nhispeed frequency, if the CPU load% based on policy frequency is not above\nhispeed load, then the information is clearly sufficient to determine that\nthe load on the CPU does not need hispeed frequency.\n\nTherefore, compute CPU load% (which is used only to compare against hispeed\nload) based on policy frequency instead of CPU target frequency.\n\nChange-Id: I1749d663949e34753ecb5c426a16563796f8b0b2\nSigned-off-by: Saravana Kannan <skannan@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/d1e778de671b545d2521de2a20f34ba4e0722c9e"},{"sha":"f49fda3b4ba08dd34c2e4b34f9af34f86fd07b24","author":{"email":"bb05168246ed1a6b66d0e7b1ffb0c5e3707764ca@codeaurora.org","name":"Junjie Wu"},"message":"cpufreq: interactive: Record hispeed_validated_time in timer function\n\nChange 0cd554ae585f5ccbb95056e049a8fec0f0742dce\n(cpufreq: interactive: Exercise hispeed settings at a policy level)\nintroduced policy level hispeed settings. The change is correct in\ngeneral, but it sets hispeed_validate_time after actual frequency\nchange has completed. Waking up speedchange task and setting\nfrequency takes non-trival amount of time. This period is not accounted\nfor in above_hispeed_delay, resulting in additional delays when\nramping up frequency. Frequency switch latency varies a lot\ndepending on beginning and end frequency, and thus it cannot be easily\ncompensated by user setting above_hispeed_delay.\n\nRecord a local hispeed_validated_time in every CPU's timer function.\nCluster hispeed_validated_time is the local hispeed_validated_time of\nCPUs voting for the highest frequency.\n\nChange-Id: Id8ae547fe3a70f8710f60b6e2125954111b7a2b6\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/f49fda3b4ba08dd34c2e4b34f9af34f86fd07b24"},{"sha":"2d3f01f86a4e85da0f619d5bf0b81aa76d9acbe9","author":{"email":"45d857216ef082c1ddfd5d3991b4f3d23f51761f@arcor.de","name":"myfluxi"},"message":"cpufreq: interactive: Honor changed minimum frequency\n\nThis saves a few cycles in the timer routine.\n\nChange-Id: I4c0e89094a00a0b63eae6320e6c3bdbb2d4c307e","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/2d3f01f86a4e85da0f619d5bf0b81aa76d9acbe9"},{"sha":"1a735dcfb0c69558d24a738aacb649c90c9504d4","author":{"email":"45d857216ef082c1ddfd5d3991b4f3d23f51761f@arcor.de","name":"myfluxi"},"message":"cpufreq: interactive: Consider changed min limit a frequency boost\n\nA changed policy->min can safely be considered a frequency boost.\nProcess this change analogous to the cpufreq_interactive_boost()\nroutine.\n\nChange-Id: Ie4ca2be2dad0f5bd541c2b79afee3bad3a349d80","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/1a735dcfb0c69558d24a738aacb649c90c9504d4"},{"sha":"7c1e5584a31c77f7c7982b4872caf6fea1bfd6bf","author":{"email":"45d857216ef082c1ddfd5d3991b4f3d23f51761f@arcor.de","name":"myfluxi"},"message":"cpufreq: interactive: Honor boosted state in several timer calculations\n\nChange-Id: If03da12c52d89a5293e32ac918db44a00ef34884","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/7c1e5584a31c77f7c7982b4872caf6fea1bfd6bf"},{"sha":"5df0755a8b1b4675b7ef77798ac74bd623e41915","author":{"email":"6f9d97df82107736b1c4f0e11d74242c25499ec8@chromium.org","name":"Andrew Bresticker"},"message":"CHROMIUM: cpufreq: interactive: validate above_hispeed_delay\n\nWe rely on the frequencies in above_hispeed_delay being in ascending\norder.  Ensure that is the case for the values the user gives us.\n\nBUG=chrome-os-partner:20830\nTEST=Boot Pit; write invalid above_hispeed_delay value:\nlocalhost ~ # echo \"20000 1800000:20000 700000:0\" > above_hispeed_delay\n-bash: echo: write error: Invalid argument\n\nChange-Id: Ifb431e58ad4b6b371152d7b09fcbefa127b0cbe2\nSigned-off-by: Andrew Bresticker <abrestic@chromium.org>\nReviewed-on: https://gerrit.chromium.org/gerrit/65742\nReviewed-by: Sonny Rao <sonnyrao@chromium.org>","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/5df0755a8b1b4675b7ef77798ac74bd623e41915"},{"sha":"41bfeb3af9d507810baa6f41c00f9ba7b3f7fa7c","author":{"email":"32f072be9e2a1650a4123445afd33554f6ea8ff4@chromium.org","name":"Bryan Freed"},"message":"CHROMIUM: Replace obsolete strict_strtoul calls.\n\nstrict_strtoul has been replaced by kstrtoul.\n\nChange-Id: I10e2a0a1b114b34283d0111e81ba5b4796d90eb0\n[bfreed: added in the 3.18 rebase]\nSigned-off-by: Bryan Freed <bfreed@chromium.org>","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/41bfeb3af9d507810baa6f41c00f9ba7b3f7fa7c"},{"sha":"9c9a115bce143cf43d61862fed63b406d1173f0a","author":{"email":"9296a0ca31e8299ed6ec39daa4ff56fd47a51cb6@codeaurora.org","name":"Rohit Gupta"},"message":"cpufreq: interactive: Rearm governor timer at max freq\n\nCurrently interactive governor timer doesn't re-arm itself when it\nselects policy->max as the new frequency to go to. On hitting idle\nfor the first time at max frequency timer is armed again. This\nmechanism doesn't have any noticeable performance benefits since\nCPUs running at max frequencies without going into idles show high\nloads which prevents the governor from lowering their frequencies.\nThis change rearms the timer even at max frequency which removes\nthe need to handle idle starts. This simplifies the code and also\nmakes the governor timer windows more regular so that the\nnotifications going out from the governor are uniformly spaced\napart. Max freq hysteresis start timestamp is refreshed everytime\npolicy->max is selected as the new frequency to prevent stepping\ndown from max frequency earlier than intended.\n\nChange-Id: I9c137113b703f2064f1e668628db91de94cc0887\nSigned-off-by: Rohit Gupta <rohgup@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/9c9a115bce143cf43d61862fed63b406d1173f0a"},{"sha":"c4467d94c23489ba4f38747b02e58db34ab0e6f7","author":{"email":"fb1ef5d447d8cd53e9e4511d7b18b7cdbb10397f@chromium.org","name":"Derek Basehore"},"message":"CHROMIUM: cpufreq: interactive: calculate load before freq change\n\nThe update to cpu load for cpufreq rate changes was happening after the rate\nchange instead of before. This switches it to update the cpu load before the\ncpufreq rate change so the old frequency is used for calculating the speed\nadjusted cpu load. The old frequency was used for that active time, so it should\nbe used for calculating the speed adjusted cpu load.\n\nBUG=chrome-os-partner:37673\nTEST=power_LoadTest on Jerry\ncheck we spend most of our time at the lower cpu frequencies\n\nChange-Id: I2fff785561ad8aebd354ddd305e91d96c799a617\nSigned-off-by: Derek Basehore <dbasehore@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/262925\nReviewed-by: Douglas Anderson <dianders@chromium.org>","distinct":true,"url":"https://api.github.com/repos/Mrcl1450/android_kernel_sony_msm8x60/commits/c4467d94c23489ba4f38747b02e58db34ab0e6f7"}]}