{"push_id":1386889848,"size":12,"distinct_size":12,"ref":"refs/heads/working","head":"80f276829b96d425cb5cbe6ea5c0e78dd0df1f49","before":"071dd836e00988d5f6998fee4468fd36cf7df5d2","commits":[{"sha":"633106628c96db26cc076821fbec2a60c511591d","author":{"name":"Junjie Wu","email":"0075153510835c15ef43801605ef8726aea51938@codeaurora.org"},"message":"msm: cpufreq: Remove acpuclock calls from cpufreq\n\nmsm-cpufreq has moved to use generic clock APIs for getting and\nsetting clock frequency. Remove the usage of deprecated acpuclock\nAPIs.\n\nChange-Id: Ia05a86a58e031a3ec4ea59cb00fba1c33cddc78b\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/tunturn/android_kernel_aries_concept/commits/633106628c96db26cc076821fbec2a60c511591d"},{"sha":"490ae25134eaff01d6dafcf043898e150dcb6377","author":{"name":"Junjie Wu","email":"0075153510835c15ef43801605ef8726aea51938@codeaurora.org"},"message":"qcom-cpufreq: Block hotplug until cpufreq is ready\n\nHotplug before qcom-cpufreq is ready could lead to inconsistent CPU\nclock state. Block hotplug by returning NOTIFY_BAD in hotplug callback\nuntil qcom-cpufreq is probed.\n\nChange-Id: I72a2f98c083c9b21b95ecafdb5a5be7a7682e842\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/tunturn/android_kernel_aries_concept/commits/490ae25134eaff01d6dafcf043898e150dcb6377"},{"sha":"763a92af34abca51123074e383f0a4e0c71a45f9","author":{"name":"Junjie Wu","email":"0075153510835c15ef43801605ef8726aea51938@codeaurora.org"},"message":"qcom-cpufreq: Fix hotplug blocking logic\n\nChange 2b63b10 qcom-cpufreq: Block hotplug until cpufreq is ready\nintended to block hotplug until qcom-cpufreq driver has got all\nclocks. However, its implementation still leaves a small window when\nCPU 0 has got its clock but others haven't. If a hotplug happens on\nanother CPU that doesn't have its clock pointer, refcount of that CPU\nclock will again be wrong.\n\nFix the issue by introducing a ready flag.\n\nChange-Id: I1e05b063b0584088f717b82709a3f1d55bc6561b\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/tunturn/android_kernel_aries_concept/commits/763a92af34abca51123074e383f0a4e0c71a45f9"},{"sha":"510d93dae1a0a2fe658c148884a05e32679eaf19","author":{"name":"Syed Rameez Mustafa","email":"d0cb06bd5d626529e5ca7f6aba1e2023bbe2ea99@codeaurora.org"},"message":"msm: cpufreq: Remove redundant check in cpu_set_freq\n\nRecent code refactoring has led to the unintentional consequence\nof having redundant checks for the success of clk_set_rate. Remove\nthe redundant check.\n\nChange-Id: I6cb7bdec15afb833519fac3232836ce9445cba48\nSigned-off-by: Syed Rameez Mustafa <rameezmustafa@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/tunturn/android_kernel_aries_concept/commits/510d93dae1a0a2fe658c148884a05e32679eaf19"},{"sha":"21dd2da2af329528fa0897f8d1bf42b91b8783af","author":{"name":"Junjie Wu","email":"0075153510835c15ef43801605ef8726aea51938@codeaurora.org"},"message":"msm: cpufreq: Remove use of cpu_is_* API\n\ncpu_is_* API is deprecated. Relevant targets now rely on is_sync for\nproper cpufreq mask setup. Remove unnecessary cpu_is_* calls from\ncpufreq.c\n\nChange-Id: I326d24c24f37b34fba36dbf9fc08aa5071180b51\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>\n(cherry picked from commit 8954ea33151f1ae91b6ed9d9909eb7f245839c07)\n(cherry picked from commit 84029ff02c16a682243b57db75fec860927a3515)","distinct":true,"url":"https://api.github.com/repos/tunturn/android_kernel_aries_concept/commits/21dd2da2af329528fa0897f8d1bf42b91b8783af"},{"sha":"1dd2f29e6677c7c42772058919990e06a2612e30","author":{"name":"Junjie Wu","email":"0075153510835c15ef43801605ef8726aea51938@codeaurora.org"},"message":"clock-a7/krait: Change initcall level for early probe\n\nRequirement to probe CPU clock drivers and register msm-cpufreq early\nmandates initcall level changes in these drivers. Order among generic\nclock driver, CPU clock driver and msm-cpufreq is unchanged, but\nCPU clock drivers and msm-cpufreq are moved to earlier level to meet\nnew requirement.\n\nChange-Id: I91c615795e2b114059d34f41b2f562a3e394e341\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/tunturn/android_kernel_aries_concept/commits/1dd2f29e6677c7c42772058919990e06a2612e30"},{"sha":"060a9016266c9dad4681df5095318e2bb95ea692","author":{"name":"Patrick Daly","email":"78479ab4153ef5619bc927755d9ca2e5cd01b75a@codeaurora.org"},"message":"clk: qcom: Allow clock-a7 to probe defer\n\nplatform_driver_probe does not allow probe deferral. Use\nplatform_driver_register instead.\n\nChange-Id: I6490c27c9b82273fa45953666f137ecb6eb0f9ee\nSigned-off-by: Patrick Daly <pdaly@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/tunturn/android_kernel_aries_concept/commits/060a9016266c9dad4681df5095318e2bb95ea692"},{"sha":"4449d58a3fc3eae6d7dc7215b832da5ce5ce28da","author":{"name":"Taniya Das","email":"1b9da212f01f05fbedbcf3a4e76243b65cdb50ea@codeaurora.org"},"message":"clk: qcom: Check return value using correct data type\n\nof_get_clk_src will contain an error value in case\nthe clk_get returns eprobe defer. Check for the correct\nreturn value.\n\nChange-Id: I0b40f6714cc55e1ad897280946d2964feb2410e0\nSigned-off-by: Taniya Das <tdas@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/tunturn/android_kernel_aries_concept/commits/4449d58a3fc3eae6d7dc7215b832da5ce5ce28da"},{"sha":"7954bafa99e33c8659e8fd2b0dfc73bac40e8109","author":{"name":"Junjie Wu","email":"0075153510835c15ef43801605ef8726aea51938@codeaurora.org"},"message":"qcom-cpufreq: Allow all CPUs to get cpu_clk on targets with sync CPUs\n\nFor targets with synchronous CPU clocks, only CPU0 has a clock pointer in\ncpu_clks[]. This forces CPU0 to be the last CPU to be hotplugged out, or go\nto certain low power mode that needs to disable CPU clocks.\n\nRemove this requirement by adding clock pointer for all CPUs. Drivers\nthat ask for CPU clocks will get same clock for CPUs in sync.\n\nChange-Id: Ib97af2c3b0fdbc8dbb78364178225cc64ed02036\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/tunturn/android_kernel_aries_concept/commits/7954bafa99e33c8659e8fd2b0dfc73bac40e8109"},{"sha":"99832df16ba67cf370fd5e9b9e2e1931b6a1e53d","author":{"name":"Matt Wagantall","email":"ac031ecf48dfa987d71856d7b1e4bc3a47e310b6@codeaurora.org"},"message":"qcom-cpufreq: Remove use of device_suspended in the hotplug path\n\nThe CPU_DOWN_PREPARE notifier in cpufreq.c already takes care\nof performing a CPUFREQ_GOV_STOP, which waits for in-progress\nfrequency switches to complete and prevents any additional\nfrequency switches from being performed. Remove the redundant\ncode for accomplishing the same thing from qcom-cpufreq.\n\nBesides being good cleanup, this change should also resolve\na potential deadlock in out-of-memory conditions. The scenario\narises if CPU1, executing in msm_cpufreq_target(), holds the\nqcom-cpufreq suspend_mutex while waiting for the completion\nat the end of that same function. In an out-of-memory condition,\nthe work performing that completion may not be able to\nimmediately run.\n\nAt the same time, CPU2 may be executing CPU_DOWN_PREPARE hotplug\nnotifiers. It will be holding the global hotplug mutex at this\ntime, and will eventually become blocked in\nmsm_cpufreq_cpu_callback() while waiting for the CPU1 to release\nthe device_suspended lock.\n\nIf invoked, the out-of-memory killer will attempt to acquire\nthe hotplug mutex via get_online_cpus() as part of\nout_of_memory().  This lock is already held by CPU2. CPU2 will\nnot release the lock until the device_suspended lock is released\nby CPU1. The device_suspended lock will not be release until the\ncompletion in msm_cpufreq_target() is marked as complete, which\nwon't happen until the out-of-memory killer is able to free\nsome memory. Nasty deadlock.\n\nClearly, the out-of-memory condition itself needs to be resolved,\nbut there is no harm in resolving the deadlock also.\n\nChange-Id: I5f59864aeb12a8c2aa81de16446af09a6d514da4\nSigned-off-by: Matt Wagantall <mattw@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/tunturn/android_kernel_aries_concept/commits/99832df16ba67cf370fd5e9b9e2e1931b6a1e53d"},{"sha":"a1230c2cf6b1f17e4f1a1dcc69a8e1d814d9aa3b","author":{"name":"myfluxi","email":"95ab61bb01957fc548ef82d227666a28af3268a6@arcor.de"},"message":"msm: cpufreq: Add pm notifiers\n\nAlso, fix a merge inconsistency that hapenend in:\nI136841405806c07e755919859e649ded0c719abb\n\nChange-Id: I6f6424cfaade24922910d1ab27a1aa341af2e10d","distinct":true,"url":"https://api.github.com/repos/tunturn/android_kernel_aries_concept/commits/a1230c2cf6b1f17e4f1a1dcc69a8e1d814d9aa3b"},{"sha":"80f276829b96d425cb5cbe6ea5c0e78dd0df1f49","author":{"name":"Junjie Wu","email":"0075153510835c15ef43801605ef8726aea51938@codeaurora.org"},"message":"qcom-cpufreq: Restore CPU frequency during resume\n\nqcom-cpufreq blocks CPU frequency change request during suspend, because\nits dependencies might be suspended. Thus a freq change request would\nfail silently, and CPU clock won't change until first frequency update\nis requested after system comes out of suspend. This creates a period\nwhen thermal driver cannot perform frequency mitigation, even though\npolicy->min/max have been correctly updated.\n\nCheck each online CPU's policy during resume to correct any frequency\nviolation as soon as possible.\n\nChange-Id: I3be79cf91e7d5e361314020c9806b770823c0b72\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/tunturn/android_kernel_aries_concept/commits/80f276829b96d425cb5cbe6ea5c0e78dd0df1f49"}]}
{"actor":{"display_login":"tunturn"}}