{"push_id":3078475241,"size":7,"distinct_size":7,"ref":"refs/heads/pie","head":"0d03d5bf39df1173c4687b79ecbc0377c0a74b40","before":"ddf132359c19347bdf541be70324e665d56227dc","commits":[{"sha":"70c4eadb7b97ebf5eda55bdebe310c78a19dd76d","author":{"name":"apophis9283","email":"d10d94ce41612a5f13ee0adbc05024eaad7da55f@gmail.com"},"message":"Kill cpu-boost","distinct":true,"url":"https://api.github.com/repos/Krieg-Kernel/OP5-OP5T/commits/70c4eadb7b97ebf5eda55bdebe310c78a19dd76d"},{"sha":"f8a8413b5c19c2567e6b9176df0fc420324370d4","author":{"name":"Sultan Alsawaf","email":"3aa1af0b84637f6957d3e83d52f23fe513bfe974@gmail.com"},"message":"msm: kgsl: Wake GPU upon receiving an ioctl rather than upon touch input\n\nWaking the GPU upon touch wastes power when the screen is being touched\nin a way that does not induce animation or any actual need for GPU usage.\nInstead of preemptively waking the GPU on touch input, wake it up upon\nreceiving a IOCTL_KGSL_GPU_COMMAND ioctl since it is a sign that the GPU\nwill soon be needed.\n\nSigned-off-by: Sultan Alsawaf <sultanxda@gmail.com>\nSigned-off-by: Atman Shah <masteratman@gmail.com>\nSigned-off-by: Dusan Uveric <dusan.uveric9@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Krieg-Kernel/OP5-OP5T/commits/f8a8413b5c19c2567e6b9176df0fc420324370d4"},{"sha":"4fb9e25ce00fcb180919465c04aeee6978375131","author":{"name":"Ray Zhang","email":"d1ea33fd8fad032de913a31cb8b09b5737d1baa1@codeaurora.org"},"message":" msm: mdss: update mdss perf when changing refresh rate\n\nRefresh rate change usually leads to different clock and\nbandwidth requirement, so update mdss perf accordingly\nbefore changing video timing to avoid underrun risk.\n\nChange-Id: I296e7672d61193bdc800efdfd4d4016c1809e894\nSigned-off-by: Ray Zhang <rayz@codeaurora.org>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\nSigned-off-by: kdrag0n <dragon@khronodragon.com>\nSigned-off-by: Dusan Uveric <dusan.uveric9@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Krieg-Kernel/OP5-OP5T/commits/4fb9e25ce00fcb180919465c04aeee6978375131"},{"sha":"b7592cdbf850a332a39fff23e6c454dc7ff54afa","author":{"name":"Dusan Uveric","email":"74dec773849a781c98e31566cbb607b0a8f3c4bf@gmail.com"},"message":"kgsl: update the effective duration of qos request\n\nSigned-off-by: Dusan Uveric <dusan.uveric9@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Krieg-Kernel/OP5-OP5T/commits/b7592cdbf850a332a39fff23e6c454dc7ff54afa"},{"sha":"375b0da4db3d4cd49835fcd6f41d2bf5e42750ec","author":{"name":"Sultan Alsawaf","email":"3aa1af0b84637f6957d3e83d52f23fe513bfe974@gmail.com"},"message":"devfreq: Introduce devfreq boost driver\n\nThis driver boosts enumerated devfreq devices upon input, and allows for\nboosting specific devfreq devices on other custom events. The boost\nfrequencies for this driver should be set so that frame drops are near-zero\nat the boosted frequencies and power consumption is minimized at said\nfrequencies. The goal of this driver is to provide an interface to achieve\noptimal device performance by requesting boosts on key events, such as when\na frame is ready to rendered to the display.\n\nCurrently, support is only present for boosting the cpubw devfreq device,\nbut the driver is structured in a way that makes it easy to add support for\nnew boostable devfreq devices in the future.\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/Krieg-Kernel/OP5-OP5T/commits/375b0da4db3d4cd49835fcd6f41d2bf5e42750ec"},{"sha":"229d4e99ca2594e6bfa0683ff8f785e03d73c809","author":{"name":"apophis9283","email":"d10d94ce41612a5f13ee0adbc05024eaad7da55f@gmail.com"},"message":"Add devfreq boost values/Fixes","distinct":true,"url":"https://api.github.com/repos/Krieg-Kernel/OP5-OP5T/commits/229d4e99ca2594e6bfa0683ff8f785e03d73c809"},{"sha":"0d03d5bf39df1173c4687b79ecbc0377c0a74b40","author":{"name":"Sultan Alsawaf","email":"3aa1af0b84637f6957d3e83d52f23fe513bfe974@gmail.com"},"message":"kernel: Boost CPU to the max when Pixel launcher becomes a top app\n\nAndroid moves the Pixel launcher process to the top-app cpuset when the\nmultitasking view is entered since this launcher handles the multitasking\ninterface, which is a very expensive interface on Pixel devices. Because of\nthis, when rapidly hitting the multitask button and switching apps\nsometimes, there's noticeably bad stuttering due to the overhead from the\napp-switch interface itself.\n\nIn order to fix the stuttering when multitasking, boost all CPUs and the\nDRAM bus to the max when the Pixel launcher is moved to the top-app cpuset.\n\nSigned-off-by: Sultan Alsawaf <sultanxda@gmail.com>\nSigned-off-by: Dusan Uveric <dusan.uveric9@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Krieg-Kernel/OP5-OP5T/commits/0d03d5bf39df1173c4687b79ecbc0377c0a74b40"}]}
{"actor":{"display_login":"APOPHIS9283"}}