{"push_id":3076915048,"size":7,"distinct_size":7,"ref":"refs/heads/version2.0_treble","head":"71a93e234bf48ddbec0db5f1d84c8a392fdd30aa","before":"352139b5eb5d485205ea091eed8569d84c892ce0","commits":[{"sha":"b0c7ca4d104ed8b8180d6d17ba320682b660fa02","author":{"name":"andip71","email":"bd67971edaf49a94837e91683b2145e95504e5dd@gmx.de"},"message":"qcom-cpufreq: ensure startup is according to default frequencies (no overclocking/underclocking)\n\nSigned-off-by: mostafa-z <mostafazarghami@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Quantisers/JaguarKernel/commits/b0c7ca4d104ed8b8180d6d17ba320682b660fa02"},{"sha":"42f84aa6d566d33a5db6c9e7fc25a90fe8e7f048","author":{"name":"Alucard24","email":"6cb58b8f5386ab909543bfc6eef5a0bd2950ca0a@gmail.com"},"message":"cpufreq: Implemented CONFIG_MSM_TRACK_FREQ_TARGET_INDEX to keep track about cpu frequency target index.\n\nSigned-off-by: mostafa-z <mostafazarghami@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Quantisers/JaguarKernel/commits/42f84aa6d566d33a5db6c9e7fc25a90fe8e7f048"},{"sha":"696257aaf7498a7fc7ec0f3a7952b287380d8619","author":{"name":"mostafa-z","email":"502c91a9caf29650b93a757c6277a56dc8d43f81@gmail.com"},"message":"cpufreq:qcom: fix Default startup frequencies for msm8940\n\nSigned-off-by: mostafa-z <mostafazarghami@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Quantisers/JaguarKernel/commits/696257aaf7498a7fc7ec0f3a7952b287380d8619"},{"sha":"3fcf307050f406b25ab017b7f38972053cf1e14d","author":{"name":"Sultan Alsawaf","email":"3aa1af0b84637f6957d3e83d52f23fe513bfe974@gmail.com"},"message":"qcom-cpufreq: Use CLKFLAG_NO_RATE_CACHE\n\nAfter a CPU comes online, clk_set_rate() silently refuses to change said CPU's\nfrequency to the frequency it was running at before going offline (since it\nthinks that we are setting the same frequency redundantly). By default, each CPU\nruns at its minimum frequency when coming online, so if the governor decides to\nkeep a CPU running at the frequency it used before going offline, then\nclk_set_rate() will ignore the frequency change request and the CPU will stay\nstuck running at its minimum frequency for a potentially long period of time\n(i.e. until the governor decides to change the frequency to something\ndifferent). This can cause severe lag when a device is woken up from deep sleep.\n\nIn order to prevent a CPU from being stuck at its default frequency for a\npotentially long period of time, set the CLKFLAG_NO_RATE_CACHE flag so that the\ngovernor's frequency change requests will always be honored right after a CPU\ncomes online.\n\nNote that this requires a CPU's component clocks to be using CLKFLAG_NO_RATE_CACHE\nas well in order to fix the issue.\n\nChange-Id: I96b7d92b9fb92863724200c7272926f49d6dcfb8\nSigned-off-by: Sultan Alsawaf <sultanxda@gmail.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Quantisers/JaguarKernel/commits/3fcf307050f406b25ab017b7f38972053cf1e14d"},{"sha":"de79445841b151d77f5fe72d0b854536e1028011","author":{"name":"Junjie Wu","email":"bb05168246ed1a6b66d0e7b1ffb0c5e3707764ca@codeaurora.org"},"message":"qcom-cpufreq: Use cpufreq_table_validate_and_show to fill freq_table\n\ncpufreq_table_validate_and_show() is created as a standard way to\ninitialize frequency for a policy and assign freq_table. Use this new\nAPI to assign freq_table.\n\nCRs-Fixed: 1024229\nChange-Id: Iac3a9394790e140492c5c0c0ad6d068840bfffa4\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>\nSigned-off-by: mostafa-z <mostafazarghami@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Quantisers/JaguarKernel/commits/de79445841b151d77f5fe72d0b854536e1028011"},{"sha":"9d563e1f4371b502bda3931a30ced07487e05070","author":{"name":"Rohit Gupta","email":"9296a0ca31e8299ed6ec39daa4ff56fd47a51cb6@codeaurora.org"},"message":"qcom-cpufreq: skip frequencies that round to same rate\n\nSince not all frequencies line up between speed bins,\nthe common cpufreq table sometimes has frequencies\nthat round up the same actual frequency.\n\nFix this by skipping those frequencies.\n\nChange-Id: I0516cc67a1343150f3d1f838b9d9b329e8e1e498\nSigned-off-by: Rohit Gupta <rohgup@codeaurora.org>\nSigned-off-by: David Keitel <dkeitel@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/Quantisers/JaguarKernel/commits/9d563e1f4371b502bda3931a30ced07487e05070"},{"sha":"71a93e234bf48ddbec0db5f1d84c8a392fdd30aa","author":{"name":"mostafa-z","email":"502c91a9caf29650b93a757c6277a56dc8d43f81@gmail.com"},"message":"cpufreq: changes to adapt for opensource clock framework\n\nUpdate cpufreq driver to adapt to opensource clock framework\nOpensource clock framework dev_clk_get returns with the\ndifferent clock handle for all cpu cores with same clock source\nThis is different in the existing clock framework where\ndev_clk_get returns with the same clock handle for the cores\nwhich shares the same clock source.\n\nCpufreq driver was compatible with the existing clock\nframework but with the opensource clock framework we need\nto handle the different clock handles for all the cores\neven the clock source is common.\n\nChange-Id: Ic343bc20dc7c8b2ce151a5a2b5f85b43cdd949bf\nSigned-off-by: Santosh Mardi <gsantosh@codeaurora.org>\nSigned-off-by: mostafa-z <mostafazarghami@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Quantisers/JaguarKernel/commits/71a93e234bf48ddbec0db5f1d84c8a392fdd30aa"}]}
{"actor":{"display_login":"Quantummech2000"}}