{"push_id":913436650,"size":11,"distinct_size":11,"ref":"refs/heads/frandom","head":"5cd3d83b0c45247df715cd934a44e17d9112cf32","before":"510e67ae85f94fc04c12be4a3dcc95ee969ce95b","commits":[{"sha":"0a1c8a19bd16bc0324c47951cc5059a766df8771","author":{"email":"d2d05c150d4a5b546ab169433b8261efde71359a@codeaurora.org","name":"Maheshwar Ajja"},"message":"msm: vidc: fix deadlock in video driver\n\nThere is deadlock between session and inst lock\nbetween response and client threads in error case.\nWhen there is session_error from video firmware,\nthe response thread acquires session lock and calls\nhandle_session_error function. At the same time\nclient thread acquired inst lock in session_close\nfunction and then calls session_clean where it is\nwaiting on session lock as it was already acquired\nby response thread. Now response thread starts\nexecuting handle_session_error function where will\ntry to acquire inst lock which was already acquired\nby client thread causing deadlock. This change resolves\ndeadlock by removing unnecessary inst lock acquiring\nby client thread in session close.\n\nSigned-off-by: Maheshwar Ajja <majja@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/G620S-HUAWEI/android_kernel_huawei_msm8916/commits/0a1c8a19bd16bc0324c47951cc5059a766df8771"},{"sha":"14b0dd22481142528fa9182e4f7fd129e8ff6d56","author":{"email":"7002fdff16c3aef9ae79c633dab0356b91a8c2e4@codeaurora.org","name":"Talel Shenhar"},"message":"mmc: core: enable BKOPS by read-modify-write instead of override\n\nThis change adds a read-modify-write logic to BKOPS feature enable.\nIt is required in order to avoid overriding other fields defined\nin BKOPS_EN register.\n\nSigned-off-by: Talel Shenhar <tatias@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/G620S-HUAWEI/android_kernel_huawei_msm8916/commits/14b0dd22481142528fa9182e4f7fd129e8ff6d56"},{"sha":"af95ffd430e68bf757978f0e655349c032700503","author":{"email":"9dca834b0a38e96a2a5a05425ca5e3d7c89ca765@codeaurora.org","name":"Ritesh Harjani"},"message":"mmc: core: Fix mmc clk scale down during writes.\n\nNo need to check for valid state when we want to\nscale down the clocks. As this state validity\ncheck is to only address that clk scaling\ndoesnt scale up (which will send tuning\ncmds) during definite cmds sequences (like\nerase operation).\n\nCRs-Fixed: 800478\nSigned-off-by: Ritesh Harjani <riteshh@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/G620S-HUAWEI/android_kernel_huawei_msm8916/commits/af95ffd430e68bf757978f0e655349c032700503"},{"sha":"23b6e2894842952e2b87b0a9797901b893219b78","author":{"email":"7002fdff16c3aef9ae79c633dab0356b91a8c2e4@codeaurora.org","name":"Talel Shenhar"},"message":"mmc: clk_scaling: add sysfs for avoiding scale down in write\n\nChange Ia7a578434d7db8983493788ab2d7f9383d703169 introduced\na degradation in performance.\nThat change tried to fix a problem for clock scaling\nduring write requests.\nDuring write request the invalid_state is always set due to\nCMD13 that is sent after each write.\nIn the attempt to fix that issue the change above added the\nability to scale down although invalid_state was set.\nThus, creating a favor for downscale over upscale.\nSome customers prefer performance over power.\nThis change introduces a sysfs entry that will allow the\ndriver to retain its old behavior which had better performance.\n\nIt can be controlled from new sysfs entry:\n\"scale_down_in_low_wr_load\" found under\n/sys/class/mmc_host/mmcX/clk_scaling/\nThe default value for it is \"0\". In case customers\nwant to gain performance over power they should set\nit to \"1\".\n\nSigned-off-by: Talel Shenhar <tatias@codeaurora.org>\n[neo: Enabled by default.]\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/G620S-HUAWEI/android_kernel_huawei_msm8916/commits/23b6e2894842952e2b87b0a9797901b893219b78"},{"sha":"82db77ee8d2172ea8bfca6c860cbd99b926fe7fe","author":{"email":"d759d83be84e44a1f85b5431666380c73349facd@motorola.com","name":"Russ W. Knize"},"message":"mmc: don't blindly retry on timed-out flushes\n\nPropagated from (CR)\n\nThe commit \"mmc: block: flush request requeue after timeout\"\nintroduced logic that blindly requeues flush requests that have\ntimed-out without checking the card state or taking advantage of\nany of the error recovery logic in the driver.  This leads to an\ninfinite loop if the card continues to time out because of how\nflush requests are prioritized over other requests.\n\nThis commit disables the retry except in the case of Hynix cards.\n\nSigned-off-by: Russ Knize <Russ.Knize@motorola.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/G620S-HUAWEI/android_kernel_huawei_msm8916/commits/82db77ee8d2172ea8bfca6c860cbd99b926fe7fe"},{"sha":"8026836a88be180637a1e1afa8f2c484b44b1d33","author":{"email":"d759d83be84e44a1f85b5431666380c73349facd@motorola.com","name":"Russ W. Knize"},"message":"mmc: improve handling of flaky SD cards\n\nPorted from (CR) on K3.0.\n\nSome cards loose their minds after many suspend/resume cycles and\nrequire more time to come to their senses.  If a card fails to\nresume, add 10ms to the settling time on each retry.\n\nSigned-off-by: Russ Knize <Russ.Knize@motorola.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/G620S-HUAWEI/android_kernel_huawei_msm8916/commits/8026836a88be180637a1e1afa8f2c484b44b1d33"},{"sha":"d800aac4506ce55a6fde359040485bce1f4244fb","author":{"email":"11e4191b1ae5cae13d3da02c22f40620ad984fdf@google.com","name":"Riley Andrews"},"message":"cpuset: Add allow_attach hook for cpusets on android.\n\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/G620S-HUAWEI/android_kernel_huawei_msm8916/commits/d800aac4506ce55a6fde359040485bce1f4244fb"},{"sha":"955f1128928cc7594956d8a093fc1f8495e9702e","author":{"email":"11e4191b1ae5cae13d3da02c22f40620ad984fdf@google.com","name":"Riley Andrews"},"message":"cpuset: Make cpusets restore on hotplug\n\nThis deliberately changes the behavior of the per-cpuset\ncpus file to not be effected by hotplug. When a cpu is offlined,\nit will be removed from the cpuset/cpus file. When a cpu is onlined,\nif the cpuset originally requested that that cpu was part of the cpuset, that\ncpu will be restored to the cpuset. The cpus files still\nhave to be hierachical, but the ranges no longer have to be out of\nthe currently online cpus, just the physically present cpus.\n\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/G620S-HUAWEI/android_kernel_huawei_msm8916/commits/955f1128928cc7594956d8a093fc1f8495e9702e"},{"sha":"c0c247ff1292353810308e79ad138a98d6524dc5","author":{"email":"d1996fe015c1f347dddf6c16199179596b8014db@codeaurora.org","name":"Naveen Ramaraj"},"message":"perf: stop deadlock when cpu_up fails\n\nWhen an attempt is made to free an event on a CPU which is\nno longer online, perf tries to bring the CPU online. This\ncan fail, resulting in an UP_CANCELLED notifier, which\neventually tries to acquire the ctx->mutex which is already\nbeing held by the cpu_up code.\n\nRemoving the attempt to bring the cpu up will remove this\ndeadlock, but also requires temporarily removing support of\ncounting events across hotplug. This will be restored in a\nlater patch.\n\nSigned-off-by: Neil Leeder <nleeder@codeaurora.org>\nSigned-off-by: Naveen Ramaraj <nramaraj@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/G620S-HUAWEI/android_kernel_huawei_msm8916/commits/c0c247ff1292353810308e79ad138a98d6524dc5"},{"sha":"57bc2316a2b1db76e6c992945ab97dae27da2c9d","author":{"email":"0a7e98000ce64542cef1b32382dcb65c847985af@codeaurora.org","name":"Prasad Sodagudi"},"message":"sched: Add a check for cpu unbound deferrable timers\n\nAdd a check for cpu unbound deferrable timer expiry and raise\nsoftirq for handling the expired timers so that the CPU can\nprocess the cpu unbound deferrable times as early as possible\nwhen a cpu tries to enter/exit idle loop.\n\nSigned-off-by: Prasad Sodagudi <psodagud@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/G620S-HUAWEI/android_kernel_huawei_msm8916/commits/57bc2316a2b1db76e6c992945ab97dae27da2c9d"},{"sha":"5cd3d83b0c45247df715cd934a44e17d9112cf32","author":{"email":"c2ec5539c4473ab294a95eac689618c01a8f4c1f@codeaurora.org","name":"Joonwoo Park"},"message":"sched: prevent task migration while governor queries CPUs' load\n\nAt present, governor retrieves each CPUs' load sequentially.  In this\nway, there is chance of race between governor's CPU load query and task\nmigration that would result in reporting of lesser CPUs' load than actual.\n\nFor example,\nCPU0 load = 30%.  CPU1 load = 50%.\nGovernor                               Load balancer\n- sched_get_busy(cpu 0) = 30%.\n                                       - A task 'p' migrated from CPU 1 to\n                                         CPU 0.  p->ravg->prev_window = 50.\n                                         Now CPU 0's load = 80%,\n                                         CPU 1's load = 0%.\n- sched_get_busy(cpu 1) = 0%\n  50% of load from CPU 1 to 0 never\n  accounted.\n\nFix such issues by introducing a new API sched_get_cpus_busy() which\nmakes for governor to be able to get set of CPUs' load.  The loads set\ninternally constructed with blocking load balancer to ensure migration\ncannot occur in the meantime.\n\nSigned-off-by: Joonwoo Park <joonwoop@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/G620S-HUAWEI/android_kernel_huawei_msm8916/commits/5cd3d83b0c45247df715cd934a44e17d9112cf32"}]}