{"push_id":1400828967,"size":46,"distinct_size":46,"ref":"refs/heads/32.2.A.0.305_RyTek--CAF-based_bcl-msmthermal","head":"add8b47cc87f4d12976802b9397c84a160a4034a","before":"e733abb435e0425921c3b518679036228dada065","commits":[{"sha":"14d140b6e7bab9533875e00c316c242705cade59","author":{"name":"Paul E. McKenney","email":"0e7edc073f39d0385f8433ab60979a97c480557c@linux.vnet.ibm.com"},"message":"rcu: Don't disable CPU hotplug during OOM notifiers\n\nRCU's rcu_oom_notify() disables CPU hotplug in order to stabilize the\nlist of online CPUs, which it traverses.  However, this is completely\npointless because smp_call_function_single() will quietly fail if invoked\non an offline CPU.  Because the count of requests is incremented in the\nrcu_oom_notify_cpu() function that is remotely invoked, everything works\nnicely even in the face of concurrent CPU-hotplug operations.\n\nFurthermore, in recent kernels, invoking get_online_cpus() from an OOM\nnotifier can result in deadlock.  This commit therefore removes the\ncall to get_online_cpus() and put_online_cpus() from rcu_oom_notify().\n\nReported-by: Marcin Ślusarz <marcin.slusarz@gmail.com>\nReported-by: David Rientjes <rientjes@google.com>\nSigned-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>\nAcked-by: David Rientjes <rientjes@google.com>\nTested-by: Marcin Ślusarz <marcin.slusarz@gmail.com>\nSigned-off-by: Srinivas Ramana <sramana@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/14d140b6e7bab9533875e00c316c242705cade59"},{"sha":"babc87a185b6f0daf8af05d25d3948fb25c005c3","author":{"name":"Srivatsa S. Bhat","email":"86fcb99d833c6028b7c159db19d83d69bb396a1e@linux.vnet.ibm.com"},"message":"CPU hotplug, smp: flush any pending IPI callbacks before CPU offline\n\nThere is a race between the CPU offline code (within stop-machine) and\nthe smp-call-function code, which can lead to getting IPIs on the\noutgoing CPU, *after* it has gone offline.\n\nSpecifically, this can happen when using\nsmp_call_function_single_async() to send the IPI, since this API allows\nsending asynchronous IPIs from IRQ disabled contexts.  The exact race\ncondition is described below.\n\nDuring CPU offline, in stop-machine, we don't enforce any rule in the\n_DISABLE_IRQ stage, regarding the order in which the outgoing CPU and\nthe other CPUs disable their local interrupts.  Due to this, we can\nencounter a situation in which an IPI is sent by one of the other CPUs\nto the outgoing CPU (while it is *still* online), but the outgoing CPU\nends up noticing it only *after* it has gone offline.\n\n              CPU 1                                         CPU 2\n          (Online CPU)                               (CPU going offline)\n\n       Enter _PREPARE stage                          Enter _PREPARE stage\n\n                                                     Enter _DISABLE_IRQ stage\n\n                                                   =\n       Got a device interrupt, and                 | Didn't notice the IPI\n       the interrupt handler sent an               | since interrupts were\n       IPI to CPU 2 using                          | disabled on this CPU.\n       smp_call_function_single_async()            |\n                                                   =\n\n       Enter _DISABLE_IRQ stage\n\n       Enter _RUN stage                              Enter _RUN stage\n\n                                  =\n       Busy loop with interrupts  |                  Invoke take_cpu_down()\n       disabled.                  |                  and take CPU 2 offline\n                                  =\n\n       Enter _EXIT stage                             Enter _EXIT stage\n\n       Re-enable interrupts                          Re-enable interrupts\n\n                                                     The pending IPI is noted\n                                                     immediately, but alas,\n                                                     the CPU is offline at\n                                                     this point.\n\nThis of course, makes the smp-call-function IPI handler code running on\nCPU 2 unhappy and it complains about \"receiving an IPI on an offline\nCPU\".\n\nOne real example of the scenario on CPU 1 is the block layer's\ncomplete-request call-path:\n\n\t__blk_complete_request() [interrupt-handler]\n\t    raise_blk_irq()\n\t        smp_call_function_single_async()\n\nHowever, if we look closely, the block layer does check that the target\nCPU is online before firing the IPI.  So in this case, it is actually\nthe unfortunate ordering/timing of events in the stop-machine phase that\nleads to receiving IPIs after the target CPU has gone offline.\n\nIn reality, getting a late IPI on an offline CPU is not too bad by\nitself (this can happen even due to hardware latencies in IPI\nsend-receive).  It is a bug only if the target CPU really went offline\nwithout executing all the callbacks queued on its list.  (Note that a\nCPU is free to execute its pending smp-call-function callbacks in a\nbatch, without waiting for the corresponding IPIs to arrive for each one\nof those callbacks).\n\nSo, fixing this issue can be broken up into two parts:\n\n1. Ensure that a CPU goes offline only after executing all the\n   callbacks queued on it.\n\n2. Modify the warning condition in the smp-call-function IPI handler\n   code such that it warns only if an offline CPU got an IPI *and* that\n   CPU had gone offline with callbacks still pending in its queue.\n\nAchieving part 1 is straight-forward - just flush (execute) all the\nqueued callbacks on the outgoing CPU in the CPU_DYING stage[1],\nincluding those callbacks for which the source CPU's IPIs might not have\nbeen received on the outgoing CPU yet.  Once we do this, an IPI that\narrives late on the CPU going offline (either due to the race mentioned\nabove, or due to hardware latencies) will be completely harmless, since\nthe outgoing CPU would have executed all the queued callbacks before\ngoing offline.\n\nOverall, this fix (parts 1 and 2 put together) additionally guarantees\nthat we will see a warning only when the *IPI-sender code* is buggy -\nthat is, if it queues the callback _after_ the target CPU has gone\noffline.\n\n[1].  The CPU_DYING part needs a little more explanation: by the time we\nexecute the CPU_DYING notifier callbacks, the CPU would have already\nbeen marked offline.  But we want to flush out the pending callbacks at\nthis stage, ignoring the fact that the CPU is offline.  So restructure\nthe IPI handler code so that we can by-pass the \"is-cpu-offline?\" check\nin this particular case.  (Of course, the right solution here is to fix\nCPU hotplug to mark the CPU offline _after_ invoking the CPU_DYING\nnotifiers, but this requires a lot of audit to ensure that this change\ndoesn't break any existing code; hence lets go with the solution\nproposed above until that is done).\n\nChange-Id: I0928593cf0bfca5972a6fcb37b943c73d5b32eb5\n[akpm@linux-foundation.org: coding-style fixes]\nSigned-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>\nSuggested-by: Frederic Weisbecker <fweisbec@gmail.com>\nCc: \"Paul E. McKenney\" <paulmck@linux.vnet.ibm.com>\nCc: Borislav Petkov <bp@suse.de>\nCc: Christoph Hellwig <hch@infradead.org>\nCc: Frederic Weisbecker <fweisbec@gmail.com>\nCc: Gautham R Shenoy <ego@linux.vnet.ibm.com>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: Mel Gorman <mgorman@suse.de>\nCc: Mike Galbraith <mgalbraith@suse.de>\nCc: Oleg Nesterov <oleg@redhat.com>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Rafael J. Wysocki <rjw@rjwysocki.net>\nCc: Rik van Riel <riel@redhat.com>\nCc: Rusty Russell <rusty@rustcorp.com.au>\nCc: Steven Rostedt <rostedt@goodmis.org>\nCc: Tejun Heo <tj@kernel.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nTested-by: Sachin Kamat <sachin.kamat@samsung.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nGit-commit: 8d056c48e486249e6487910b83e0f3be7c14acf7\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\n[sramana@codeaurora.org: merge conflicts resolved while porting to msm-3.10]\nSigned-off-by: Srinivas Ramana <sramana@codeaurora.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/babc87a185b6f0daf8af05d25d3948fb25c005c3"},{"sha":"832fcf3af891379ef7214fe77344ef8a017c8af5","author":{"name":"Tommy-Geenexus","email":"4ad1e7c13388d78ac01a12342c329880d5c18abd@gmail.com"},"message":"soc: msm_performance: rename max CPU freq module name\n* To prevent post-boot-scripts from messing with max CPU freq","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/832fcf3af891379ef7214fe77344ef8a017c8af5"},{"sha":"a3a613d4fa16ab057e3b780be5b3f576162bf335","author":{"name":"Ram Chandrasekar","email":"344cad9e385e8e08d46dcc942c3cc4e2a6503b1f@codeaurora.org"},"message":"power: bcl: Use real-time workqueue for hotplug\n\nUse real-time workqueue for hotplug operation. This\nwill make sure that hotplug happens at high priority\nand doesnt cause priority inversion issue with thermal\nreal time threads\n\nChange-Id: I2f3a1023fca279a1043d7e3491f25de0be7f90e1\nSigned-off-by: Ram Chandrasekar <rkumbako@codeaurora.org>\nSigned-off-by: RyTek <rytek1128@outlook.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/a3a613d4fa16ab057e3b780be5b3f576162bf335"},{"sha":"12e8dcd83778cb2263bf4508b70ca7fce271c0f4","author":{"name":"Ram Chandrasekar","email":"344cad9e385e8e08d46dcc942c3cc4e2a6503b1f@codeaurora.org"},"message":"power: bcl_peripheral: Add ftrace events\n\nAdd ftrace events to bcl driver events. Events are\nadded in the places where the registers are read/write,\nwhen interrupts are triggered and bcl state changes.\n\nCRs-Fixed: 760435\nChange-Id: I53985292a3bccb9a2e33f144528c56f4d659205a\nSigned-off-by: Ram Chandrasekar <rkumbako@codeaurora.org>\nSigned-off-by: RyTek <rytek1128@outlook.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/12e8dcd83778cb2263bf4508b70ca7fce271c0f4"},{"sha":"687b77505fab791ddee1effdaf6d1aa314fb85cd","author":{"name":"Ram Chandrasekar","email":"344cad9e385e8e08d46dcc942c3cc4e2a6503b1f@codeaurora.org"},"message":"power: bcl: Add ftrace events\n\nAdd ftrace events when battery parameter change\nis notified, when mitigation is initiated and\ncleared.\n\nCRs-Fixed: 760435\nChange-Id: I901d8e737f9ba2150ef7c2a9c19bbcf79e93c0e6\nSigned-off-by: Ram Chandrasekar <rkumbako@codeaurora.org>\nSigned-off-by: RyTek <rytek1128@outlook.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/687b77505fab791ddee1effdaf6d1aa314fb85cd"},{"sha":"6d97fb99cb144df41157d2f15127b9f399e0642f","author":{"name":"Manaf Meethalavalappu Pallikunhi","email":"c206658a52c2fe0fb598c46fb7b56eaea5d1c35e@codeaurora.org"},"message":"power: bcl: Update threshold type before queuing hotplug work\n\nCurrently threshold types of Vbat and Ibat are updated after queuing\nhotplug work event. There is a possibility of using previous threshold\ntype in hotplug work if hotplug work event get scheduled immediately.\nUpdate current threshold type for Vbat and Ibat before queuing\nhotplug work event.\n\nChange-Id: Iecf5c3a514fa2b008f798fe4bd3ed46249ec8d4b\nSigned-off-by: Manaf Meethalavalappu Pallikunhi <manafm@codeaurora.org>\nSigned-off-by: RyTek <rytek1128@outlook.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/6d97fb99cb144df41157d2f15127b9f399e0642f"},{"sha":"7873e87c41a422766def7bead5c8b2acf8af042c","author":{"name":"Shiju Mathew","email":"562b9af727c18a381d2d514e0438a344ba960f5a@codeaurora.org"},"message":"power: bcl: Do BCL core mitigation via KTM interface\n\nThis patch will do BCL core mitigation via KTM device\nmanager interface. This will reduce core mitigation\ncontention between KTM and BCL.\n\nChange-Id: Ie4bb85c1ea91120d1de4618f214bdc24724e5e7a\nSigned-off-by: Shiju Mathew <shijum@codeaurora.org>\nSigned-off-by: RyTek <rytek1128@outlook.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/7873e87c41a422766def7bead5c8b2acf8af042c"},{"sha":"e828637bd9f594f1823e565bd1ef321a17046929","author":{"name":"Shiju Mathew","email":"562b9af727c18a381d2d514e0438a344ba960f5a@codeaurora.org"},"message":"power: bcl: Add ftrace events for bcl mitigation\n\nAdd ftrace events in bcl driver for frequency and\nhotplug mitigations.\n\nChange-Id: I76a968f8b752c66c06a7af8b517d22a32cf6eeda\nSigned-off-by: Shiju Mathew <shijum@codeaurora.org>\nSigned-off-by: RyTek <rytek1128@outlook.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/e828637bd9f594f1823e565bd1ef321a17046929"},{"sha":"8000f4a8bcbc363c241db94a5f18fc6d514f4de8","author":{"name":"Manaf Meethalavalappu Pallikunhi","email":"c206658a52c2fe0fb598c46fb7b56eaea5d1c35e@codeaurora.org"},"message":"power: bcl: Add soc low threshold sysfs node to BCL driver\n\nAdd soc low threshold sysfs node to add support for configuring\nsoc low threshold at runtime. It adds below sysfs node\n'/sys/devices/soc.0/qcom,bcl.*/soc_low_thresh'.\n\nChange-Id: I4debc34ddde63bc0f842384e03715bc60ddcc59a\nSigned-off-by: Manaf Meethalavalappu Pallikunhi <manafm@codeaurora.org>\nSigned-off-by: RyTek <rytek1128@outlook.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/8000f4a8bcbc363c241db94a5f18fc6d514f4de8"},{"sha":"b8b67120c6c29371a63f03784bcd743d4127b1c4","author":{"name":"Manaf Meethalavalappu Pallikunhi","email":"c206658a52c2fe0fb598c46fb7b56eaea5d1c35e@codeaurora.org"},"message":"power: bcl: Check battery state of charge for frequency mitigation\n\nWhen BCL monitoring is disabled, the SoC monitoring state is reset\nbut the last read value is not reset. During BCL frequency mitigation,\nit always checks the last read soc value against configured BCL soc\nthreshold. This will allow the SoC based frequency mitigation to be\nactive, even when BCL is disabled. Use BCL soc state instead of\nthe last read battery SoC value to place soc frequency mitigation.\n\nChange-Id: I2b1a171b0bc00cbb4f7029c8de2aaa4817573b49\nSigned-off-by: Manaf Meethalavalappu Pallikunhi <manafm@codeaurora.org>\nSigned-off-by: RyTek <rytek1128@outlook.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/b8b67120c6c29371a63f03784bcd743d4127b1c4"},{"sha":"20f467a0c7b778a7f39a3075e8161a087fe1bddf","author":{"name":"David Keitel","email":"60136972b62d1ff1557476805ac04157a53f41a9@codeaurora.org"},"message":"bcl: fix allocation for BCL attribute\n\nThe size of the BCL attribute is incorrect due to a precedence bug:\n\nThis was observed while booting with Kernel Address Sanitizer(KASan) enabled.\n\n=============================================================================\nBUG kmalloc-64 (Tainted: G    B       ): kasan: bad access detected\n-----------------------------------------------------------------------------\n\nINFO: Slab 0xffffffbc0661c6e0 objects=64 used=64 fp=0x          (null) flags=0x0080\nINFO: Object 0xffffffc0a360bb00 @offset=2816 fp=0xffffffc0a3454728\n\nBytes b4 ffffffc0a360baf0: 3f 37 9c 1c 00 00 00 00 02 00 02 00 a9 4e ad de  ?7...........N..\nObject ffffffc0a360bb00: 28 47 45 a3 c0 ff ff ff 48 47 45 a3 c0 ff ff ff  (GE.....HGE.....\nObject ffffffc0a360bb10: 68 47 45 a3 c0 ff ff ff 00 00 00 00 00 00 00 00  hGE.............\nObject ffffffc0a360bb20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\nObject ffffffc0a360bb30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\nCPU: 0 PID: 1 Comm: swapper/0 Tainted: G    B        3.10.49-g465b172-00133-gb931dc1 #134\nCall trace:\n[<ffffffc00040a2a4>] dump_backtrace+0x0/0x1d4\n[<ffffffc00040a488>] show_stack+0x10/0x1c\n[<ffffffc000f971a4>] dump_stack+0x1c/0x28\n[<ffffffc00054aeb4>] print_trailer+0x144/0x158\n[<ffffffc00054b210>] object_err+0x38/0x4c\n[<ffffffc00054fed8>] kasan_report_error+0x210/0x3b0\n[<ffffffc000550188>] kasan_report+0x68/0x78\n[<ffffffc00054f1b0>] __asan_load8+0x90/0x9c\n[<ffffffc0005dff78>] internal_create_group+0x1a0/0x2f4\n[<ffffffc0005e00dc>] sysfs_create_group+0x10/0x1c\n[<ffffffc000c5eb9c>] msm_bcl_register_param+0x384/0x450\n[<ffffffc000c61758>] bcl_probe+0x840/0xb84\n[<ffffffc000a394b8>] spmi_drv_probe+0x2c/0x3c\n[<ffffffc000999150>] driver_probe_device+0x1f4/0x47c\n[<ffffffc0009994c4>] __driver_attach+0x88/0xc0\n[<ffffffc000996434>] bus_for_each_dev+0xdc/0x11c\n[<ffffffc0009988ac>] driver_attach+0x2c/0x3c\n[<ffffffc0009981fc>] bus_add_driver+0x1bc/0x32c\n[<ffffffc000999d1c>] driver_register+0x10c/0x1d8\n[<ffffffc000a39a30>] spmi_driver_register+0x98/0xa8\n[<ffffffc00183a300>] bcl_perph_init+0x2c/0x38\n[<ffffffc000400b00>] do_one_initcall+0xcc/0x188\n[<ffffffc001800b54>] kernel_init_freeable+0x1c0/0x264\n[<ffffffc000f89b84>] kernel_init+0x10/0xcc\nMemory state around the buggy address:\n ffffffc0a360ba00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n ffffffc0a360ba80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n>ffffffc0a360bb00: 00 00 00 01 fc fc fc fc fc fc fc fc fc fc fc fc\n                            ^\n ffffffc0a360bb80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n ffffffc0a360bc00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n==================================================================\n\nFix this by adding parantheses to fix precedence.\n\nCRs-Fixed: 826589\nChange-Id: Ia58b6e52c491b89b10a2b8fe45445372bfe9fa20\nSigned-off-by: David Keitel <dkeitel@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/20f467a0c7b778a7f39a3075e8161a087fe1bddf"},{"sha":"c6df5fc2ac498762404aa6e9bb01cd02ac7aeeb3","author":{"name":"Patrick Daly","email":"78479ab4153ef5619bc927755d9ca2e5cd01b75a@codeaurora.org"},"message":"bcl: Fix lockdep warnings\n\nProperly initialize dynamically allocated sysfs attributes.\n\n[    1.305450] BUG: key ffffffc0627cc4c0 not in .data!\n[    1.305460] ------------[ cut here ]------------\n[    1.305479] WARNING: at kernel/lockdep.c:2987\n\t\t\t\tlockdep_init_map+0x154/0x4c8()\n[    1.305487] DEBUG_LOCKS_WARN_ON(1)\n[    1.305497] CPU: 4 PID: 1 Comm: swapper/0 Not tainted\n[    1.305507] Call trace:\n[    1.305519] [<ffffffc0000888b4>] dump_backtrace+0x0/0x258\n[    1.305528] [<ffffffc000088b28>] show_stack+0x1c/0x28\n[    1.305539] [<ffffffc000dc6a88>] dump_stack+0x1c/0x28\n[    1.305549] [<ffffffc00009fbe8>] warn_slowpath_common+0x78/0x9c\n[    1.305557] [<ffffffc00009fcb4>] warn_slowpath_fmt+0x74/0x84\n[    1.305564] [<ffffffc000109898>] lockdep_init_map+0x150/0x4c8\n[    1.305575] [<ffffffc0001fccf4>] sysfs_add_file_mode+0x90/0x100\n[    1.305583] [<ffffffc0001ffe3c>] internal_create_group+0x138/0x1c8\n[    1.305590] [<ffffffc0001ffef4>] sysfs_create_group+0x28/0x38\n[    1.305601] [<ffffffc0007584a4>] msm_bcl_register_param+0x254/0x2f0\n\nChange-Id: Iaae034361bafe47fb72b116614c8158f041ce17b\nSigned-off-by: Patrick Daly <pdaly@codeaurora.org>\nSigned-off-by: RyTek <rytek1128@outlook.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/c6df5fc2ac498762404aa6e9bb01cd02ac7aeeb3"},{"sha":"6e293baf1c8d447a059e202f70d81905f95155f0","author":{"name":"Ram Chandrasekar","email":"344cad9e385e8e08d46dcc942c3cc4e2a6503b1f@codeaurora.org"},"message":"power: bcl_peripheral: Update the ADC to vbat conversion formula\n\nUpdate the ADC value to battery voltage conversion formula\nto accommodate the 2 LSB ADC value error. Without this\ncorrection, the existing formula was estimating a lower\nbattery voltage by 2 LSB ADC value.\n\nCRs-Fixed: 919926\nChange-Id: Ibfffbbb8923504c30bdc4032db27f19d0a00e808\nSigned-off-by: Ram Chandrasekar <rkumbako@codeaurora.org>\nSigned-off-by: RyTek <rytek1128@outlook.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/6e293baf1c8d447a059e202f70d81905f95155f0"},{"sha":"20ad12e9d94adc21fffbc121fc2ace54a6415e91","author":{"name":"Ram Chandrasekar","email":"344cad9e385e8e08d46dcc942c3cc4e2a6503b1f@codeaurora.org"},"message":"msm: thermal: Use phandle to input the cluster cpu map\n\nModify to use cpu phandles to input cluster and\ncpu mapping.\n\nUse of static bit-mask wont work well with removing\ncpus during run time. With the new implementation, KTM\nusing phandles, will try to map the physical cores to\nthe corresponding logical cores to establish the cluster\ncpu mask.\n\nChange-Id: Id1fa76be35c2c70bf0d98408bd3ae5fc4c108cbd\nSigned-off-by: Ram Chandrasekar <rkumbako@codeaurora.org>\nSigned-off-by: RyTek <rytek1128@outlook.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/20ad12e9d94adc21fffbc121fc2ace54a6415e91"},{"sha":"cdaf851267986e979a96c4bcc6bde8084cdd82d4","author":{"name":"Manaf Meethalavalappu Pallikunhi","email":"c206658a52c2fe0fb598c46fb7b56eaea5d1c35e@codeaurora.org"},"message":"msm: thermal: Use CPU phandles instead of cpu mask in KTM\n\nUse CPU phandles to map the physical cores to the corresponding\nlogical cores for all cpu mask related nodes in KTM. This will\nensure KTM will mitigate even if a CPU is removed or the physical\nto logical core mapping is altered.\n\nChange-Id: Ic225c5079aca301cdaf85fa568c3d7329b9f1f63\nSigned-off-by: Manaf Meethalavalappu Pallikunhi <manafm@codeaurora.org>\nSigned-off-by: RyTek <rytek1128@outlook.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/cdaf851267986e979a96c4bcc6bde8084cdd82d4"},{"sha":"4956d2e831bce8b3768e50f09fc47166dc886797","author":{"name":"Jeff Bernard","email":"5bdea4d1d4bd123ab5a78f1681afe71248b1fe54@codeaurora.org"},"message":"msm: thermal: Add scaling factor for thermal sensors\n\nAdd a scale factor to scale the temperature and\nset points for asics that have a different thermal\nsensor accuracy.\n\nOn MSM Thulium temperature sensors report in deci degree\nC while previous asics report in degree C. KTM expects\nthe temperature in C.\n\nChange-Id: I1a94652de48e1fb69164dfc63764a346333ca849\nSigned-off-by: Jeff Bernard <jbernard@codeaurora.org>\n[imaund@codeaurora.org: Resolved context conflicts, updated\n  instances of hi_temp to high_temp]\nSigned-off-by: Ian Maund <imaund@codeaurora.org>\n\nSigned-off-by: RyTek <rytek1128@outlook.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/4956d2e831bce8b3768e50f09fc47166dc886797"},{"sha":"67d7c70d808de1fa1d8f5d58b7631ae12f93636b","author":{"name":"Manaf Meethalavalappu Pallikunhi","email":"c206658a52c2fe0fb598c46fb7b56eaea5d1c35e@codeaurora.org"},"message":"msm: thermal: Fix KTM code to check psm is enabled before handling it\n\nDuring boot up polling mode mitigation, KTM handles psm code even if\nfeature is disabled. Add a check in psm code whether feature is enabled\nor not before handling this.\n\nChange-Id: I55d6ed43e829dbf8a35cf8af4a3ca28cfb10c013\nSigned-off-by: Manaf Meethalavalappu Pallikunhi <manafm@codeaurora.org>\nSigned-off-by: RyTek <rytek1128@outlook.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/67d7c70d808de1fa1d8f5d58b7631ae12f93636b"},{"sha":"38ad5959456fb16e523075d1511a89a0a0119733","author":{"name":"Shiju Mathew","email":"562b9af727c18a381d2d514e0438a344ba960f5a@codeaurora.org"},"message":"msm: thermal: Update scm calls in KTM with non-atomic calls\n\nUpdate KTM to use scm_call() and scm_call2()instead\nof scm_call_atomic1() and scm_call2_atomic()\nrespectively to avoid possible race condition.\n\nCRs-fixed: 734431\nChange-Id: Ibb81c4c15a47d1f66ffa38cb65481e3c48fcb065\nSigned-off-by: Shiju Mathew <shijum@codeaurora.org>\nSigned-off-by: RyTek <rytek1128@outlook.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/38ad5959456fb16e523075d1511a89a0a0119733"},{"sha":"e43982a3f942bc6d46cd8dc8910cfb50bfdb117e","author":{"name":"Ram Chandrasekar","email":"344cad9e385e8e08d46dcc942c3cc4e2a6503b1f@codeaurora.org"},"message":"msm: thermal: Retry on failure to hotplug\n\nAdd support in thermal driver to retry hotplug\nrequest on failure to fulfill the request.\n\nThis retrying will be disabled when the device\nenters suspend and will resume after the device\nexits from suspend.\n\nChange-Id: I9e2c305754465eb458566c0224804c5ad4bda240\nSigned-off-by: Ram Chandrasekar <rkumbako@codeaurora.org>\nSigned-off-by: RyTek <rytek1128@outlook.com>","distinct":true,"url":"https://api.github.com/repos/RyTekk/sony_kernel_kitakami_8994/commits/e43982a3f942bc6d46cd8dc8910cfb50bfdb117e"}]}
{"actor":{"display_login":"RyTekk"}}