{"push_id":2894287351,"size":138,"distinct_size":138,"ref":"refs/heads/staging/O-KernelX","head":"72426da8fe93438402851ca062d70db39dd8423b","before":"f4061b1ffd2dc2366dab300a3e948bd0fd92f0f5","commits":[{"sha":"c3bc2f7c870c804cc3105455388631cb5ded2b3f","author":{"name":"Sultan Alsawaf","email":"3aa1af0b84637f6957d3e83d52f23fe513bfe974@gmail.com"},"message":"proc: Remove verifiedbootstate flag from /proc/cmdline\n\nUserspace parses this and sets the ro.boot.verifiedbootstate prop\naccording to the value that this flag has. When ro.boot.verifiedbootstate\nis not 'green', SafetyNet is tripped and fails the CTS test.\n\nHide verifiedbootstate from /proc/cmdline in order to fix the failed\nSafetyNet CTS check.\n\nSigned-off-by: Sultan Alsawaf <sultanxda@gmail.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/c3bc2f7c870c804cc3105455388631cb5ded2b3f"},{"sha":"2e56f1cb3cf3290363d7c84c299db8e9c3165fa7","author":{"name":"Sultan Alsawaf","email":"3aa1af0b84637f6957d3e83d52f23fe513bfe974@gmail.com"},"message":"proc: Remove additional SafetyNet flags from /proc/cmdline\n\nSafetyNet checks androidboot.veritymode in Nougat, so remove it.\n\nAdditionally, remove androidboot.enable_dm_verity and androidboot.secboot\nin case SafetyNet will check them in the future.\n\nSigned-off-by: Sultan Alsawaf <sultanxda@gmail.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/2e56f1cb3cf3290363d7c84c299db8e9c3165fa7"},{"sha":"c88b34dbf357fb06482c035417abc8f65008ea61","author":{"name":"Joel Fernandes","email":"89f39a38232ac523c7644e47b6ca6563177e40b4@google.com"},"message":"cpufreq: schedutil: Make iowait boost more energy efficient\n\nCurrently the iowait_boost feature in schedutil makes the frequency\ngo to max on iowait wakeups.  This feature was added to handle a case\nthat Peter described where the throughput of operations involving\ncontinuous I/O requests [1] is reduced due to running at a lower\nfrequency, however the lower throughput itself causes utilization to\nbe low and hence causing frequency to be low hence its \"stuck\".\n\nInstead of going to max, its also possible to achieve the same effect\nby ramping up to max if there are repeated in_iowait wakeups\nhappening. This patch is an attempt to do that. We start from a lower\nfrequency (policy->min) and double the boost for every consecutive\niowait update until we reach the maximum iowait boost frequency\n(iowait_boost_max).\n\nI ran a synthetic test (continuous O_DIRECT writes in a loop) on an\nx86 machine with intel_pstate in passive mode using schedutil.  In\nthis test the iowait_boost value ramped from 800MHz to 4GHz in 60ms.\nThe patch achieves the desired improved throughput as the existing\nbehavior.\n\n[1] https://patchwork.kernel.org/patch/9735885/\n\nSuggested-by: Peter Zijlstra <peterz@infradead.org>\nSuggested-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Joel Fernandes <joelaf@google.com>\nAcked-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/c88b34dbf357fb06482c035417abc8f65008ea61"},{"sha":"e8be225387df55b13308c8e2ad6b01bbcdc84e8c","author":{"name":"Joel Fernandes","email":"89f39a38232ac523c7644e47b6ca6563177e40b4@google.com"},"message":"cpufreq: schedutil: Use unsigned int for iowait boost\n\nMake iowait_boost and iowait_boost_max as unsigned int since its unit\nis kHz and this is consistent with struct cpufreq_policy.  Also change\nthe local variables in sugov_iowait_boost() to match this.\n\nSigned-off-by: Joel Fernandes <joelaf@google.com>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/e8be225387df55b13308c8e2ad6b01bbcdc84e8c"},{"sha":"20e89db23e818faee022b5e00bc21b867acb2925","author":{"name":"Viresh Kumar","email":"5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org"},"message":"cpufreq: Return 0 from ->fast_switch() on errors\n\nCPUFREQ_ENTRY_INVALID is a special symbol which is used to specify that\nan entry in the cpufreq table is invalid. But using it outside of the\nscope of the cpufreq table looks a bit incorrect.\n\nWe can represent an invalid frequency by writing it as 0 instead if we\nneed. Note that it is already done that way for the return value of the\n->get() callback.\n\nLets do the same for ->fast_switch() and not use CPUFREQ_ENTRY_INVALID\noutside of the scope of cpufreq table.\n\nAlso update the comment over cpufreq_driver_fast_switch() to clearly\nmention what this returns.\n\nNone of the drivers return CPUFREQ_ENTRY_INVALID as of now from\n->fast_switch() callback and so we don't need to update any of those.\n\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/20e89db23e818faee022b5e00bc21b867acb2925"},{"sha":"f02ecde7097040a38dc11146f1bb8916476213ff","author":{"name":"Viresh Kumar","email":"5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org"},"message":"cpufreq: schedutil: Reset cached_raw_freq when not in sync with next_freq\n\n'cached_raw_freq' is used to get the next frequency quickly but should\nalways be in sync with sg_policy->next_freq. There is a case where it is\nnot and in such cases it should be reset to avoid switching to incorrect\nfrequencies.\n\nConsider this case for example:\n\n - policy->cur is 1.2 GHz (Max)\n - New request comes for 780 MHz and we store that in cached_raw_freq.\n - Based on 780 MHz, we calculate the effective frequency as 800 MHz.\n - We then see the CPU wasn't idle recently and choose to keep the next\n   freq as 1.2 GHz.\n - Now we have cached_raw_freq is 780 MHz and sg_policy->next_freq is\n   1.2 GHz.\n - Now if the utilization doesn't change in then next request, then the\n   next target frequency will still be 780 MHz and it will match with\n   cached_raw_freq. But we will choose 1.2 GHz instead of 800 MHz here.\n\nFixes: b7eaf1aab9f8 (cpufreq: schedutil: Avoid reducing frequency of busy CPUs prematurely)\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nCc: 4.12+ <stable@vger.kernel.org> # 4.12+\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/f02ecde7097040a38dc11146f1bb8916476213ff"},{"sha":"dca20044680e331d4bf8a975b7f71c1fdb8e9266","author":{"name":"Patrick Bellasi","email":"431c86f368affbc3148c4669fbd465131f7e82cb@arm.com"},"message":"cpufreq: schedutil: Fix iowait boost reset\n\nA more energy efficient update of the IO wait boosting mechanism has\nbeen introduced in:\n\n   commit a5a0809bc58e (\"cpufreq: schedutil: Make iowait boost more energy efficient\")\n\nwhere the boost value is expected to be:\n\n - doubled at each successive wakeup from IO\n   staring from the minimum frequency supported by a CPU\n\n - reset when a CPU is not updated for more then one tick\n   by either disabling the IO wait boost or resetting its value to the\n   minimum frequency if this new update requires an IO boost.\n\nThis approach is supposed to \"ignore\" boosting for sporadic wakeups from\nIO, while still getting the frequency boosted to the maximum to benefit\nlong sequence of wakeup from IO operations.\n\nHowever, these assumptions are not always satisfied.\nFor example, when an IO boosted CPU enters idle for more the one tick\nand then wakes up after an IO wait, since in sugov_set_iowait_boost() we\nfirst check the IOWAIT flag, we keep doubling the iowait boost instead\nof restarting from the minimum frequency value.\n\nThis misbehavior could happen mainly on non-shared frequency domains,\nthus defeating the energy efficiency optimization, but it can also\nhappen on shared frequency domain systems.\n\nLet fix this issue in sugov_set_iowait_boost() by:\n - first check the IO wait boost reset conditions\n   to eventually reset the boost value\n - then applying the correct IO boost value\n   if required by the caller\n\nFixes: a5a0809bc58e (cpufreq: schedutil: Make iowait boost more energy efficient)\nReported-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Patrick Bellasi <patrick.bellasi@arm.com>\nReviewed-by: Joel Fernandes (Google) <joel@joelfernandes.org>\nAcked-by: Viresh Kumar <viresh.kumar@linaro.org>\nAcked-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/dca20044680e331d4bf8a975b7f71c1fdb8e9266"},{"sha":"876941b8b95e29719c565c1180927352d895d41d","author":{"name":"Rafael J. Wysocki","email":"27ffc44a8ec6a212fba98cfc3246c6ce8ab131e0@intel.com"},"message":"cpufreq: schedutil: Avoid using invalid next_freq\n\nIf the next_freq field of struct sugov_policy is set to UINT_MAX,\nit shouldn't be used for updating the CPU frequency (this is a\nspecial \"invalid\" value), but after commit b7eaf1aab9f8 (cpufreq:\nschedutil: Avoid reducing frequency of busy CPUs prematurely) it\nmay be passed as the new frequency to sugov_update_commit() in\nsugov_update_single().\n\nFix that by adding an extra check for the special UINT_MAX value\nof next_freq to sugov_update_single().\n\nFixes: b7eaf1aab9f8 (cpufreq: schedutil: Avoid reducing frequency of busy CPUs prematurely)\nReported-by: Viresh Kumar <viresh.kumar@linaro.org>\nCc: 4.12+ <stable@vger.kernel.org> # 4.12+\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nAcked-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/876941b8b95e29719c565c1180927352d895d41d"},{"sha":"aa151cddf9e0eae0f8ba0a67a1cb14505008bb53","author":{"name":"Juri Lelli","email":"bdc6bcd4e8b34b4b92413d758024aeca6da0e459@arm.com"},"message":"UPSTREAM: cpufreq: schedutil: use now as reference when aggregating shared policy requests\n\nCurrently, sugov_next_freq_shared() uses last_freq_update_time as a\nreference to decide when to start considering CPU contributions as\nstale.\n\nHowever, since last_freq_update_time is set by the last CPU that issued\na frequency transition, this might cause problems in certain cases. In\npractice, the detection of stale utilization values fails whenever the\nCPU with such values was the last to update the policy. For example (and\nplease note again that the SCHED_CPUFREQ_RT flag is not the problem\nhere, but only the detection of after how much time that flag has to be\nconsidered stale), suppose a policy with 2 CPUs:\n\n               CPU0                |               CPU1\n                                   |\n                                   |     RT task scheduled\n                                   |     SCHED_CPUFREQ_RT is set\n                                   |     CPU1->last_update = now\n                                   |     freq transition to max\n                                   |     last_freq_update_time = now\n                                   |\n\n                        more than TICK_NSEC nsecs\n\n                                   |\n     a small CFS wakes up          |\n     CPU0->last_update = now1      |\n     delta_ns(CPU0) < TICK_NSEC*   |\n     CPU0's util is considered     |\n     delta_ns(CPU1) =              |\n      last_freq_update_time -      |\n      CPU1->last_update = 0        |\n      < TICK_NSEC                  |\n     CPU1 is still considered      |\n     CPU1->SCHED_CPUFREQ_RT is set |\n     we stay at max (until CPU1    |\n     exits from idle)              |\n\n* delta_ns is actually negative as now1 > last_freq_update_time\n\nWhile last_freq_update_time is a sensible reference for rate limiting,\nit doesn't seem to be useful for working around stale CPU states.\n\nFix the problem by always considering now (time) as the reference for\ndeciding when CPUs have stale contributions.\n\nBug: 109836581\nSigned-off-by: Juri Lelli <juri.lelli@arm.com>\nAcked-by: Vincent Guittot <vincent.guittot@linaro.org>\nAcked-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\n(cherry picked from commit https://github.com/aosp-mirror/kernel_common/commit/d86ab9cff8b936aadde444d0e263a8db5ff0349b)\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/aa151cddf9e0eae0f8ba0a67a1cb14505008bb53"},{"sha":"0e1ac6f9d865c9c7815afc39a1b1e1841cf8e1ea","author":{"name":"Sultan Alsawaf","email":"3aa1af0b84637f6957d3e83d52f23fe513bfe974@gmail.com"},"message":"kernel: Add API to mark IRQs and kthreads as performance critical\n\nOn devices with a CPU that contains heterogeneous cores (e.g., big.LITTLE),\nit can be beneficial to place some performance-critical IRQs and kthreads\nonto the performance CPU cluster in order to improve performance.\n\nThis commit adds the following APIs:\n-kthread_run_perf_critical() to create and start a perf-critical kthread\n-IRQF_PERF_CRITICAL to schedule an IRQ and any threads it may have onto\n performance CPUs\n-PF_PERF_CRITICAL to mark a process (mainly kthread) as performance\n critical (this is used by kthread_run_perf_critical())\n\nIn order to accomodate this new API, the following changes are made:\n-Performance-critical IRQs have their affinities reaffined upon exit from\n suspend (since the affinities are broken when non-boot CPUs are disabled)\n-Performance-critical IRQs and their threads have their affinities reset\n upon entering suspend, so that upon immediate suspend exit (when only the\n boot CPU is online), interrupts can be processed and interrupt threads\n can be scheduled onto an online CPU (otherwise we'd hit a kernel BUG)\n-Global cpu_lp_mask and cpu_perf_mask symbols are added to provide\n a cpumask of low-power and performance CPUs, respectively. This is\n set to the big.LITTLE layout used on msm8998 by default.\n-do_set_cpus_allowed() and __set_cpus_allowed_ptr() are modified to enforce\n a performance-critical kthread's affinity\n-Mark perf-critical IRQs with IRQD_AFFINITY_MANAGED so userspace can't mess\n with their affinity\n\nSigned-off-by: Sultan Alsawaf <sultanxda@gmail.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/0e1ac6f9d865c9c7815afc39a1b1e1841cf8e1ea"},{"sha":"91a30fc29ec72b8e6eadb325708f3e0e82fc17bf","author":{"name":"Sultan Alsawaf","email":"3aa1af0b84637f6957d3e83d52f23fe513bfe974@gmail.com"},"message":"kernel: Force trivial, unbound kthreads onto low-power CPUs\n\nIn order to reduce power consumption, force all non-perf-critical, unbound\nkthreads onto the low-power CPUs. Note that init (pid == 1) must be\nexplicitly excluded from this so that all processes forked from init have a\nsane default CPU affinity mask.\n\nSigned-off-by: Sultan Alsawaf <sultanxda@gmail.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/91a30fc29ec72b8e6eadb325708f3e0e82fc17bf"},{"sha":"9fb5aa52ecb0f90e85e01d531b0407e89ada816f","author":{"name":"Sultan Alsawaf","email":"3aa1af0b84637f6957d3e83d52f23fe513bfe974@gmail.com"},"message":"msm: kgsl: Mark IRQ and worker thread as performance critical\n\nThese items are in the critical path for rendering frames to the display,\nso mark them as performance-critical.\n\nSigned-off-by: Sultan Alsawaf <sultanxda@gmail.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/9fb5aa52ecb0f90e85e01d531b0407e89ada816f"},{"sha":"86602e678178c58b1234234aae96f57dfe9f867e","author":{"name":"Francisco Franco","email":"42480b5f4d505650064e5081b85d867a03559887@gmail.com"},"message":"drm: msm: Mark IRQ and important kthreads as performance critical\n\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/86602e678178c58b1234234aae96f57dfe9f867e"},{"sha":"2fa205710d867e45d341564fdff266cc66e288a8","author":{"name":"Sultan Alsawaf","email":"3aa1af0b84637f6957d3e83d52f23fe513bfe974@gmail.com"},"message":"cpu_input_boost: Introduce driver for event-based CPU boosting\n\nThis is a clean CPU input boost driver that boosts all online CPUs for a\nfixed amount of time. Additionally, there is an API for other drivers to\nrequest a boost kick, so boosting can be done on any custom event. This API\nis mainly intended for the framebuffer driver to send a boost kick whenever\nthere is a new frame ready to be rendered to the display.\n\nThis driver also boosts all online CPUs to their maximum frequencies when\nthe display is powered on (this is the wake boost).\n\nSince this driver requires careful tuning for optimal performance, there\nare no user-exposed knobs to configure it. All necessary configuration is\ndone via the supplied Kconfig options.\n\nThis driver is designed for heterogeneous multi-processor systems with two\nCPU clusters.\n\nSigned-off-by: Sultan Alsawaf <sultanxda@gmail.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/2fa205710d867e45d341564fdff266cc66e288a8"},{"sha":"bf585ee90746070ceca074b18954964bd3e54d3d","author":{"name":"Francisco Franco","email":"42480b5f4d505650064e5081b85d867a03559887@gmail.com"},"message":"cpu_input_boost: add an option to choose a custom boost finish return freq for the LP cluster\n\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/bf585ee90746070ceca074b18954964bd3e54d3d"},{"sha":"8aee5e2f66edf0e70badc95e2a7e97b962e782d6","author":{"name":"Nathan Chancellor","email":"f65d3f2dc139dcfe7b6f0b0a466af3bc5fed8fa7@gmail.com"},"message":"cpu_input_boost: Add ability to choose minimum frequency for big cluster\n\nAlso, make sure we choose the actual minimum frequency if the configs\nare at their default value of zero using the maximum of the two.\n\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/8aee5e2f66edf0e70badc95e2a7e97b962e782d6"},{"sha":"6536efea943eeada955db8238001af954e26426b","author":{"name":"Francisco Franco","email":"42480b5f4d505650064e5081b85d867a03559887@gmail.com"},"message":"cpu_input_boost: expose input freqs and duration to userspace\n\nUsers like to change stuff and it's useful to tie it in with my\nPerformance Profiles and it's faster to test new configurations\nthan recompiling the whole thing and flash every time.\n\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/6536efea943eeada955db8238001af954e26426b"},{"sha":"3a44a430c7dec319a364069ec3313c3c52aeca1a","author":{"name":"Francisco Franco","email":"42480b5f4d505650064e5081b85d867a03559887@gmail.com"},"message":"cpu_input_boost: make the userspace module param vars static\n\nAccording to Sultan without them being static it pollutes the\nglobal symbol list and reduces the compiler's ability to optimize.\n\nReported-by: Sultan Alsawaf <sultanxda@gmail.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/3a44a430c7dec319a364069ec3313c3c52aeca1a"},{"sha":"f559611c5ab77bba54a7df915a8a8c1329f93f7d","author":{"name":"Sultan Alsawaf","email":"3aa1af0b84637f6957d3e83d52f23fe513bfe974@gmail.com"},"message":"cpu_input_boost: Add API for boosting all CPUs to max frequency\n\nThis adds the cpu_input_boost_kick_max() function, which will boost all\nonline CPUs to their respective maximum frequencies for the requested\nduration in milliseconds. Wake boosts take precedence over boost kicks\nrequested via cpu_input_boost_kick_max() so that these boost kicks cannot\naccidentally shorten the duration of a wake boost.\n\nSigned-off-by: Sultan Alsawaf <sultanxda@gmail.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/f559611c5ab77bba54a7df915a8a8c1329f93f7d"},{"sha":"145144e123723252893ae747edf3b38d256d0833","author":{"name":"Sultan Alsawaf","email":"3aa1af0b84637f6957d3e83d52f23fe513bfe974@gmail.com"},"message":"cpu_input_boost: Fix and refactor max boost logic\n\nInstead of just preventing cpu_input_boost_kick_max() from erroneously\nshortening a wake boost, prevent it from erroneously shortening any\nrequested max boost. This allows multiple boost sources to request\ndifferent max boost durations without the risk of accidentally trampling on\nother max boosts.\n\nAdditionally, clean up the max boost invocation for wake boosts and make\nit use the correct duration.\n\nSigned-off-by: Sultan Alsawaf <sultanxda@gmail.com>\nSigned-off-by: Nathan Chancellor <natechancellor@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Hlcpereira/kernel_xiaomi_sdm845/commits/145144e123723252893ae747edf3b38d256d0833"}]}
{"actor":{"display_login":"Hlcpereira"}}