{"push_id":825745210,"size":32,"distinct_size":32,"ref":"refs/heads/android-6.0","head":"698d4cc024506749ce278ad09e470986b38490f7","before":"bb833bca959beeb788ad5784804f28182c174f4e","commits":[{"sha":"292b34238312185e3a026a2308211c412d1b0832","author":{"email":"50cb9bee76fd6567c3233b8a89e4a594c545792f@gmail.com","name":"flar2"},"message":"touchscreen: increase wakeup delay","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/292b34238312185e3a026a2308211c412d1b0832"},{"sha":"45513c153166f740ffbbfa72298ed08a5003ac18","author":{"email":"742cc7da48fa788d384ec77ccfb9a4657661404c@gmail.com","name":"imoseyon"},"message":"power: smb135x: bump up 300-400mA for PC/USB charging\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/45513c153166f740ffbbfa72298ed08a5003ac18"},{"sha":"c1e9879d67cb8dee5b201defd38d10210d3d3ea0","author":{"email":"3fddac958924aef220f202ca567388ddab3f14a8@infradead.org","name":"Peter Zijlstra"},"message":"sched, smp: Correctly deal with nested sleeps\n\nsmp_hotplug_thread::{setup,unpark} functions can sleep too, so be\nconsistent and do the same for all callbacks.\n\n __might_sleep+0x74/0x80\n kmem_cache_alloc_trace+0x4e/0x1c0\n perf_event_alloc+0x55/0x450\n perf_event_create_kernel_counter+0x2f/0x100\n watchdog_nmi_enable+0x8d/0x160\n watchdog_enable+0x45/0x90\n smpboot_thread_fn+0xec/0x2b0\n kthread+0xe4/0x100\n ret_from_fork+0x7c/0xb0\n\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: tglx@linutronix.de\nCc: ilya.dryomov@inktank.com\nCc: umgwanakikbuti@gmail.com\nCc: oleg@redhat.com\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nLink: http://lkml.kernel.org/r/20140924082242.392279328@infradead.org\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/c1e9879d67cb8dee5b201defd38d10210d3d3ea0"},{"sha":"5fc81f12b61d515fc076e5d4df92192568a72a9b","author":{"email":"50cb9bee76fd6567c3233b8a89e4a594c545792f@gmail.com","name":"flar2"},"message":"Fix version name\n\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/5fc81f12b61d515fc076e5d4df92192568a72a9b"},{"sha":"d6461e1dfb6d3c1f71f31f63b4c56f5824a97fb1","author":{"email":"9edab3d8932dbb8f20eb55cd8199c20e7fb56c12@oracle.com","name":"Jeff Liu"},"message":"binfmt_elf.c: use get_random_int() to fix entropy depleting\n\nChanges:\n--------\nv4->v3:\n- s/random_stack_user()/get_atrandom_bytes()/\n- Move this function to ahead of its use to avoid the predeclaration.\n\nv3->v2:\n- Tweak code comments of random_stack_user().\n- Remove redundant bits mask and shift upon the random variable.\n\nv2->v1:\n- Fix random copy to check up buffer length that are not 4-byte multiples.\n\nv3 can be found at:\nhttp://www.spinics.net/lists/linux-fsdevel/msg59597.html\nv2 can be found at:\nhttp://www.spinics.net/lists/linux-fsdevel/msg59418.html\nv1 can be found at:\nhttp://www.spinics.net/lists/linux-fsdevel/msg59128.html\n\nThanks,\n-Jeff\n\nEntropy is quickly depleted under normal operations like ls(1), cat(1),\netc...  between 2.6.30 to current mainline, for instance:\n\n$ cat /proc/sys/kernel/random/entropy_avail\n3428\n$ cat /proc/sys/kernel/random/entropy_avail\n2911\n$cat /proc/sys/kernel/random/entropy_avail\n2620\n\nWe observed this problem has been occurring since 2.6.30 with\nfs/binfmt_elf.c: create_elf_tables()->get_random_bytes(), introduced by\nf06295b44c296c8f (\"ELF: implement AT_RANDOM for glibc PRNG seeding\").\n\n/*\n * Generate 16 random bytes for userspace PRNG seeding.\n */\nget_random_bytes(k_rand_bytes, sizeof(k_rand_bytes));\n\nThe patch introduces a wrapper around get_random_int() which has lower\noverhead than calling get_random_bytes() directly.\n\nWith this patch applied:\n$ cat /proc/sys/kernel/random/entropy_avail\n2731\n$ cat /proc/sys/kernel/random/entropy_avail\n2802\n$ cat /proc/sys/kernel/random/entropy_avail\n2878\n\nAnalyzed by John Sobecki.\n\nSigned-off-by: Jie Liu <jeff.liu@oracle.com>\nCc: Andrew Morton <akpm@linux-foundation.org>\nCc: Al Viro <viro@zeniv.linux.org.uk>\nCc: Andreas Dilger <aedilger@gmail.com>\nCc: Alan Cox <alan@linux.intel.com>\nCc: Arnd Bergmann <arnn@arndb.de>\nCc: John Sobecki <john.sobecki@oracle.com>\nCc: James Morris <james.l.morris@oracle.com>\nCc: Jakub Jelinek <jakub@redhat.com>\nCc: Ted Ts'o <tytso@mit.edu>\nCc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nCc: Kees Cook <keescook@chromium.org>\nCc: Ulrich Drepper <drepper@redhat.com>\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/d6461e1dfb6d3c1f71f31f63b4c56f5824a97fb1"},{"sha":"d048df687989e4b205f2ff34e01b72509a272be7","author":{"email":"42480b5f4d505650064e5081b85d867a03559887@gmail.com","name":"franciscofranco"},"message":"msm: thermal: add a module param to change the thermal throttle temperature point to userspace\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/d048df687989e4b205f2ff34e01b72509a272be7"},{"sha":"570e34c5c648e1a252a1032d8cd86573d35fa24d","author":{"email":"4d9e23a041ac966f5316a7481300d4ae12e806fe@redhat.com","name":"Dave Chinner"},"message":"sync: don't block the flusher thread waiting on IO\n\nWhen sync does it's WB_SYNC_ALL writeback, it issues data Io and\nthen immediately waits for IO completion. This is done in the\ncontext of the flusher thread, and hence completely ties up the\nflusher thread for the backing device until all the dirty inodes\nhave been synced. On filesystems that are dirtying inodes constantly\nand quickly, this means the flusher thread can be tied up for\nminutes per sync call and hence badly affect system level write IO\nperformance as the page cache cannot be cleaned quickly.\n\nWe already have a wait loop for IO completion for sync(2), so cut\nthis out of the flusher thread and delegate it to wait_sb_inodes().\nHence we can do rapid IO submission, and then wait for it all to\ncomplete.\n\nEffect of sync on fsmark before the patch:\n\nFSUse%        Count         Size    Files/sec     App Overhead\n.....\n     0       640000         4096      35154.6          1026984\n     0       720000         4096      36740.3          1023844\n     0       800000         4096      36184.6           916599\n     0       880000         4096       1282.7          1054367\n     0       960000         4096       3951.3           918773\n     0      1040000         4096      40646.2           996448\n     0      1120000         4096      43610.1           895647\n     0      1200000         4096      40333.1           921048\n\nAnd a single sync pass took:\n\n  real    0m52.407s\n  user    0m0.000s\n  sys     0m0.090s\n\nAfter the patch, there is no impact on fsmark results, and each\nindividual sync(2) operation run concurrently with the same fsmark\nworkload takes roughly 7s:\n\n  real    0m6.930s\n  user    0m0.000s\n  sys     0m0.039s\n\nIOWs, sync is 7-8x faster on a busy filesystem and does not have an\nadverse impact on ongoing async data write operations.\n\nSigned-off-by: Dave Chinner <dchinner@redhat.com>\nReviewed-by: Jan Kara <jack@suse.cz>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/570e34c5c648e1a252a1032d8cd86573d35fa24d"},{"sha":"ea599cf227deaeefde93fe1fc6916fb33872d54f","author":{"email":"adb0658383f88ec6beb1fb7689ba0dac7c1c4882@oracle.com","name":"Junxiao Bi"},"message":"writeback: fix race that cause writeback hung\n\nThere is a race between mark inode dirty and writeback thread, see the\nfollowing scenario.  In this case, writeback thread will not run though\nthere is dirty_io.\n\n__mark_inode_dirty()                                          bdi_writeback_workfn()\n\t...                                                       \t...\n\tspin_lock(&inode->i_lock);\n\t...\n\tif (bdi_cap_writeback_dirty(bdi)) {\n\t    <<< assume wb has dirty_io, so wakeup_bdi is false.\n\t    <<< the following inode_dirty also have wakeup_bdi false.\n\t    if (!wb_has_dirty_io(&bdi->wb))\n\t\t    wakeup_bdi = true;\n\t}\n\tspin_unlock(&inode->i_lock);\n\t                                                            <<< assume last dirty_io is removed here.\n\t                                                            pages_written = wb_do_writeback(wb);\n\t                                                            ...\n\t                                                            <<< work_list empty and wb has no dirty_io,\n\t                                                            <<< delayed_work will not be queued.\n\t                                                            if (!list_empty(&bdi->work_list) ||\n\t                                                                (wb_has_dirty_io(wb) && dirty_writeback_interval))\n\t                                                                queue_delayed_work(bdi_wq, &wb->dwork,\n\t                                                                    msecs_to_jiffies(dirty_writeback_interval * 10));\n\tspin_lock(&bdi->wb.list_lock);\n\tinode->dirtied_when = jiffies;\n\t<<< new dirty_io is added.\n\tlist_move(&inode->i_wb_list, &bdi->wb.b_dirty);\n\tspin_unlock(&bdi->wb.list_lock);\n\n\t<<< though there is dirty_io, but wakeup_bdi is false,\n\t<<< so writeback thread will not be waked up and\n\t<<< the new dirty_io will not be flushed.\n\tif (wakeup_bdi)\n\t    bdi_wakeup_thread_delayed(bdi);\n\nWriteback will run until there is a new flush work queued.  This may cause\na lot of dirty pages stay in memory for a long time.\n\nSigned-off-by: Junxiao Bi <junxiao.bi@oracle.com>\nReviewed-by: Jan Kara <jack@suse.cz>\nCc: Fengguang Wu <fengguang.wu@intel.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/ea599cf227deaeefde93fe1fc6916fb33872d54f"},{"sha":"e9e49e0ca0f7b4d5774d2b917a32a0b209451974","author":{"email":"65d484aa1efdaf0ae258f87a04ed8ec8685cba3e@samsung.com","name":"Namjae Jeon"},"message":"writeback: fix writeback cache thrashing\n\nConsider Process A: huge I/O on sda\n        doing heavy write operation - dirty memory becomes more\n        than dirty_background_ratio\n        on HDD - flusher thread flush-8:0\n\nConsider Process B: small I/O on sdb\n        doing while [1]; read 1024K + rewrite 1024K + sleep 2sec\n        on Flash device - flusher thread flush-8:16\n\nAs Process A is a heavy dirtier, dirty memory becomes more\nthan dirty_background_thresh. Due to this, below check becomes\ntrue(checking global_page_state in over_bground_thresh)\nfor all bdi devices(even for very small dirtied bdi - sdb):\n\nIn this case, even small cached data on 'sdb' is forced to flush\nand writeback cache thrashing happens.\n\nWhen we added debug prints inside above 'if' condition and ran\nabove Process A(heavy dirtier on bdi with flush-8:0) and\nProcess B(1024K frequent read/rewrite on bdi with flush-8:16)\nwe got below prints:\n\n[Test setup: ARM dual core CPU, 512 MB RAM]\n\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  56064 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  56704 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 84720 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 94720 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   384 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   960 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =    64 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 92160 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   256 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   768 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =    64 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   256 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   320 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =     0 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 92032 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 91968 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   192 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =  1024 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =    64 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   192 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   576 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =     0 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 84352 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   192 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =   512 KB\n[over_bground_thresh]: wakeup flush-8:16 : BDI_RECLAIMABLE =     0 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 92608 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE = 92544 KB\n\nAs mentioned in above log, when global dirty memory > global background_thresh\nsmall cached data is also forced to flush by flush-8:16.\nIf removing global background_thresh checking code, we can reduce cache\nthrashing of frequently used small data.\nAnd It will be great if we can reserve a portion of writeback cache using\nmin_ratio.\n\nAfter applying patch:\n$ echo 5 > /sys/block/sdb/bdi/min_ratio\n$ cat /sys/block/sdb/bdi/min_ratio\n5\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  56064 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  56704 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  84160 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  96960 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  94080 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  93120 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  93120 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  91520 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  89600 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  93696 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  93696 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  72960 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  90624 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  90624 KB\n[over_bground_thresh]: wakeup flush-8:0 : BDI_RECLAIMABLE =  90688 KB\n\nAs mentioned in the above logs, once cache is reserved for Process B,\nand patch is applied there is less writeback cache thrashing on sdb\nby frequent forced writeback by flush-8:16 in over_bground_thresh.\n\nAfter all, small cached data will be flushed by periodic writeback\nonce every dirty_writeback_interval.\n\nSuggested-by: Wanpeng Li <liwanp@linux.vnet.ibm.com>\nSigned-off-by: Namjae Jeon <namjae.jeon@samsung.com>\nSigned-off-by: Vivek Trivedi <t.vivek@samsung.com>\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/e9e49e0ca0f7b4d5774d2b917a32a0b209451974"},{"sha":"ad549669a767bc839cdaa2fbf959daf0fb39243c","author":{"email":"24f7fe9d205c8a9f6ade0c2894e14303ca16087f@intel.com","name":"Fengguang Wu"},"message":"readahead: make context readahead more conservative\n\nThis helps performance on moderately dense random reads on SSD.\n\nTransaction-Per-Second numbers provided by Taobao:\n\n\t\tQPS\tcase\n\t\t-------------------------------------------------------\n\t\t7536\tdisable context readahead totally\nw/ patch:\t7129\tslower size rampup and start RA on the 3rd read\n\t\t6717\tslower size rampup\nw/o patch:\t5581\tunmodified context readahead\n\nBefore, readahead will be started whenever reading page N+1 when it happen\nto read N recently.  After patch, we'll only start readahead when *three*\nrandom reads happen to access pages N, N+1, N+2.  The probability of this\nhappening is extremely low for pure random reads, unless they are very\ndense, which actually deserves some readahead.\n\nAlso start with a smaller readahead window.  The impact to interleaved\nsequential reads should be small, because for a long run stream, the the\nsmall readahead window rampup phase is negletable.\n\nThe context readahead actually benefits clustered random reads on HDD\nwhose seek cost is pretty high.  However as SSD is increasingly used for\nrandom read workloads it's better for the context readahead to concentrate\non interleaved sequential reads.\n\nAnother SSD rand read test from Miao\n\n        # file size:        2GB\n        # read IO amount: 625MB\n        sysbench --test=fileio          \\\n                --max-requests=10000    \\\n                --num-threads=1         \\\n                --file-num=1            \\\n                --file-block-size=64K   \\\n                --file-test-mode=rndrd  \\\n                --file-fsync-freq=0     \\\n                --file-fsync-end=off    run\n\nshows the performance of btrfs grows up from 69MB/s to 121MB/s, ext4 from\n104MB/s to 121MB/s.\n\nSigned-off-by: Wu Fengguang <fengguang.wu@intel.com>\nTested-by: Tao Ma <tm@tao.ma>\nTested-by: Miao Xie <miaox@cn.fujitsu.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/ad549669a767bc839cdaa2fbf959daf0fb39243c"},{"sha":"18e8efbd70b087a34636f1daeefb9efdd7ab756f","author":{"email":"596727c8a0ea4db3ba2ceceedccbacd3d7b371b8@suse.cz","name":"Jan Kara"},"message":"block: Reserve only one queue tag for sync IO if only 3 tags are available\n\nIn case a device has three tags available we still reserve two of them\nfor sync IO. That leaves only a single tag for async IO such as\nwriteback from flusher thread which results in poor performance.\n\nAllow async IO to consume two tags in case queue has three tag availabe\nto get a decent async write performance.\n\nThis patch improves streaming write performance on a machine with such disk\nfrom ~21 MB/s to ~52 MB/s. Also postmark throughput in presence of\nstreaming writer improves from 8 to 12 transactions per second so sync\nIO doesn't seem to be harmed in presence of heavy async writer.\n\nSigned-off-by: Jan Kara <jack@suse.cz>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/18e8efbd70b087a34636f1daeefb9efdd7ab756f"},{"sha":"9ea91f63149c9735a3f593f18c2aa6fceb89d46c","author":{"email":"45d857216ef082c1ddfd5d3991b4f3d23f51761f@arcor.de","name":"myfluxi"},"message":"msm: kgsl: Report correct GPU frequency in sysfs\n\nChange-Id: I1aac90d0554b9de0511ffb78042177a5a23855ce\n\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/9ea91f63149c9735a3f593f18c2aa6fceb89d46c"},{"sha":"050c0b91a4e307e376c15b9fbf2c8385ed1ecb3f","author":{"email":"2e473c16998297376fa93aaaf19bfd6462656788@codeaurora.org","name":"Gaurav Gagrani"},"message":"msm: kgsl: enable CPU IRQ while suspending context\n\nMake sure that CPU interrupt is enabled before calling adreno\nsuspend_context when moving from NAP/SLEEP to SLUMBER state.\nWe send commands to GPU in adreno_drawctxt_switch() which will generate\nGPU interrupt. Since CPU interrupt is not enabled, adreno_idle() will\nfail because pending interrupt will not be served by CPU this causes\nfalse GPU hang.\n\nCRs-Fixed: 547813\n\nChange-Id: Ia4b730b8f8cda1e820f571ffb7ddb00336ca1a8c\nSigned-off-by: Gaurav Gagrani <ggagrani@codeaurora.org>\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/050c0b91a4e307e376c15b9fbf2c8385ed1ecb3f"},{"sha":"c2ee9b68f3a97f127cef2cf941c22c1c57ccf5cf","author":{"email":"80d5042ab220b9b7f8135930b3a092662230c31e@codeaurora.org","name":"Xiaoming Zhou"},"message":"msm: mdss: properly handle panel on and off\n\nThere is some condition that panel off will be called multiple times.\nIn this case, it was blindly free the gpios that were already released.\nThis is adding the check to handle this condition.\n\nChange-Id: I0140872be1255fe00ed5abd164a246fa57b2a245\nSigned-off-by: Xiaoming Zhou <zhoux@codeaurora.org>\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/c2ee9b68f3a97f127cef2cf941c22c1c57ccf5cf"},{"sha":"94eec6796e745fc51b7bd6f8f5ceaf065af23210","author":{"email":"3cf0f186520a9ded19b3ad376b389fe60b55f4ed@codeaurora.org","name":"Suman Tatiraju"},"message":"msm: kgsl: set the correct max_state\n\nMax_state from the driver should be set to the number of power\nlevels. The devfreq governor then checks the frequencies from\n0 to max_state -1.\n\nChange-Id: I79a6da698ff8bcb2840774ccc5d792b7ddbf126b\nSigned-off-by: Suman Tatiraju <sumant@codeaurora.org>\n\nConflicts:\n\tdrivers/gpu/msm/kgsl_pwrscale.c\nSigned-off-by: flar2 <asegaert@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/94eec6796e745fc51b7bd6f8f5ceaf065af23210"},{"sha":"e71fd0d3375b909c699c5406dbc14e56562199f2","author":{"email":"50cb9bee76fd6567c3233b8a89e4a594c545792f@gmail.com","name":"flar2"},"message":"msm_hsic_host: reduce wakelock","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/e71fd0d3375b909c699c5406dbc14e56562199f2"},{"sha":"e62551da127149491a1bae6ad69699ad980374d1","author":{"email":"bfdf9f1f58ab0baf2612c45989055a4282facf06@codeaurora.org","name":"Anish Kumar"},"message":"ASoC: wcd9xxx: use hwdep node for codec calibration\n\nCurrently codec driver uses request_firmware to get\ncalibration data but as this firmware file is also written by\nuserspace process after bootup, it is not recommended to\nuse request_firmware. ALSA core provides mechanism to get\nhardware dependant data using hwdep nodes. Tomtom codec will\nuse aforementioned nodes to get calibration data from userspace.\n\nChanged ANC calibration data size\n\nSigned-off-by: Anish Kumar <kanish@codeaurora.org>\nSigned-off-by: Pavan Chikkala <pavanc@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/e62551da127149491a1bae6ad69699ad980374d1"},{"sha":"f4edc7f0568f8224a633dc4ace55f5c92bd2e30e","author":{"email":"082104a2214aa7a3388a958bfb417cb349d77515@codeaurora.org","name":"Divya Narayanan Poojary"},"message":"ASoC: wcd9320: fix the no audio issue on triggering SSR\n\nAfter the SSR is triggered there is possibility of the  mismatch\namong  the cache register values and the actual hardware registers\nvalues. Due to this some of the registers doesn't gets updated when\nthe enable sequence is triggered. This results incomplete path\ngetting enabled resulting in no audio.\nFix by updating the registers to the reset state and updating the\ncache also. Also restart the mbhc for the proper headset detection\n\nSigned-off-by: Aviral Gupta <aviralg@codeaurora.org>\nSigned-off-by: Divya Narayanan Poojary <dnaray@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/f4edc7f0568f8224a633dc4ace55f5c92bd2e30e"},{"sha":"931442778f58e54fa1943e985e38e837840bde61","author":{"email":"0898c4e5c8d849879fa65e9f23cfa9cb45bd5a93@codeaurora.org","name":"Phani Kumar Uppalapati"},"message":"ASoC: core: call digital mute ops for capture use case\n\nCurrently digital mute ops are called only for playback\nuse cases. Add support to call into codec digital mute\neven for capture use cases.\n\nSigned-off-by: Phani Kumar Uppalapati <phaniu@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/931442778f58e54fa1943e985e38e837840bde61"},{"sha":"20bb0a1daa305c36102e0fd82e0b896c215549f3","author":{"email":"0898c4e5c8d849879fa65e9f23cfa9cb45bd5a93@codeaurora.org","name":"Phani Kumar Uppalapati"},"message":"ASoC: core: Remove sound card state check from read/write\n\nHaving sound card offline condition checks inside\nregister read/write functions will also avoid Asoc\ncache writes. However, it is needed to update the\nAsoc cache whenever user-space sends disable sequence\nwhile sound card is in offline state. Remove the offline\ncheck condition from ASoC read/writes and let the codec\ndriver take care of not sending bus read/writes if sound\ncard is in offline state.\n\nSigned-off-by: Phani Kumar Uppalapati <phaniu@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/kabata1975/Emotion_Shamu_M/commits/20bb0a1daa305c36102e0fd82e0b896c215549f3"}]}