{"push_id":736769301,"size":11,"distinct_size":11,"ref":"refs/heads/cm-12.1","head":"04032784908530a4f17dbdd413f3a36792bb2c70","before":"1c2bdc027d4200aa8b7ccaf394329f947e038cd1","commits":[{"sha":"205992e1fa278cb68094e36a316d38ebca6be7e2","author":{"email":"41bb5944f244750b7cf0394140496972a3f1bee3@intel.com","name":"Adrian Hunter"},"message":"mmc: core: move ->request() call from atomic context\n\nmmc_request_done() is sometimes called from interrupt or other atomic\ncontext.  Mostly all mmc_request_done() does is complete(), however it\ncontains code to retry on error, which uses ->request().  As the error\npath is certainly not performance critical, this may be moved to the\nwaiting function mmc_wait_for_req().\n\nThis allows ->request() to use runtime PM get_sync() and guarantee it\nis never in an atomic context.\n\nChange-Id: I9cdb0f4a25568949a2c65dda59adba7728c585d1\nSigned-off-by: Adrian Hunter <adrian.hunter@intel.com>\nAcked-by: Ulf Hansson <ulf.hansson@stericsson.com>\nSigned-off-by: Chris Ball <cjb@laptop.org>\nSigned-off-by: Konstantin Dorfman <kdorfman@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/MCP1/android_kernel_motorola_msm8960-common/commits/205992e1fa278cb68094e36a316d38ebca6be7e2"},{"sha":"d1b204c8b545326f43e197850dd8dd5d333929a9","author":{"email":"fd5f0306a6bff8c35f448543fbef2801a1315f85@motorola.com","name":"kbarath"},"message":"mmc: TRIM WAR for Toshiba\n\nToshiba 24nm (eMMC v4.41) parts perform poorly when issued TRIM\ncommands because they do synchronous garbage collection.  Falling\nback on normal erase commands works around this, since the part will\nonly do a logical remapping of the erased block.  This is resolved\non their 19nm (eMMC v4.5) parts.\nChange-Id: If49539c9ab03e9eaeefaba7d62d1505e72022287\nSigned-off-by: Russ Knize <Russ.Knize@motorola.com>","distinct":true,"url":"https://api.github.com/repos/MCP1/android_kernel_motorola_msm8960-common/commits/d1b204c8b545326f43e197850dd8dd5d333929a9"},{"sha":"20862e9e3edea9aef272ef3c844f13ca7b755ece","author":{"email":"2375fa63e2908bb2df59f606483a3aa92321db7a@doshaska.net","name":"nadlabak"},"message":"Revert \"Revert \"mmc: core: Prevent too long response times for suspend\"\"\n\nThis reverts commit a4582d64f0f197392467e6519e4cc1aa46736206.\n\nChange-Id: I1f13778d476446e6e3d3d1784042c6c9d6c4ca67","distinct":true,"url":"https://api.github.com/repos/MCP1/android_kernel_motorola_msm8960-common/commits/20862e9e3edea9aef272ef3c844f13ca7b755ece"},{"sha":"1485fe171994a73bc1bb305458bf57803804a83c","author":{"email":"fe47b31f388f85ce6ddf64bf3a0cf6b46077d0e6@stericsson.com","name":"Ulf Hansson"},"message":"mmc: core: Fixup suspend/resume issues for UHS-I cards\n\nEven if cards supports 1.8V I/O voltage those should anyway be\ninitialized at 3.3V I/O according to (e)MMC, SD and SDIO specs.\nSome eMMC and embedded SDIO devices are able to be initialized\nat 1.8V as well, but it is better to be safe.\n\nDo note that initialization in this context means that the card\nhas been completely powered off, otherwise the card will remain\nat the last I/O voltage level that were negotitiated.\n\nDue to the above being taken care of the suspend/resume issues\nfor UHS-I SD-cards has been fixed.\n\nChange-Id: I3c6076e98632ca692a223933aac89bb1341dd0f6\nSigned-off-by: Ulf Hansson <ulf.hansson@stericsson.com>\nAcked-by: Philip Rakity <prakity@marvell.com>\nAcked-by: Linus Walleij <linus.walleij@linaro.org>\nTested-by: Subhash Jadavani <subhashj@codeaurora.org>\nSigned-off-by: Chris Ball <cjb@laptop.org>","distinct":true,"url":"https://api.github.com/repos/MCP1/android_kernel_motorola_msm8960-common/commits/1485fe171994a73bc1bb305458bf57803804a83c"},{"sha":"1fb00e91c4c3481b7acae9f4b43c7a83979eeae7","author":{"email":"d09719b174b1d7232763de9bbeaca66508591b55@codeaurora.org","name":"Sujit Reddy Thumma"},"message":"mmc: msm_sdcc: Fix race in disabling sdcc core irq\n\no Assume SDCC driver has SDIO clients attached and\n  runtime clock gating has turned off the SDCC clocks.\n\no Now, if the SDIO client driver has initiated a request\n  to SDCC and since the clocks are turned off, mmc framework\n  tries to turn them on calling msmsdcc_set_ios().\n\no msmsdcc_set_ios() tries to disable the core irq first and\n  reenable after the clocks are turned on. While in process\n  of disabling the irq, if there is an asynchronous notification\n  from SDIO client h/w, it will preempt ongoing disable and run\n  msmsdcc_irq() which internally does disable_irq_nosync() since\n  the clocks are still off.\n\no While the control returns to msmsdcc_set_ios() from preemption\n  it will continue disabling the core irq (even though\n  host->sdcc_irq_disabled = 1). In effect, calls disable_irq()\n  twice increasing the irq desc->depth to 2.\n\no The enable_irq() API enables the irq in h/w if and only if\n  desc->depth = 1, and hence become a noop if it is called with\n  desc->depth = 2 causing sdcc failure because the interrupts\n  are not enabled in h/w.\n\nFix the above race condition by making sure disable irq is done\natomically.\n\nCRs-Fixed: 357406\nChange-Id: Id8a4e5cc9b0ac035a83c070ede57b2c39d96e6e9\nSigned-off-by: Sujit Reddy Thumma <sthumma@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/MCP1/android_kernel_motorola_msm8960-common/commits/1fb00e91c4c3481b7acae9f4b43c7a83979eeae7"},{"sha":"98f1ba2b114b9664647c746690e7a2956e980a6a","author":{"email":"54c033d5e34885de636f902627b260d3e5278396@motorola.com","name":"Russ 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\nChange-Id: I376b79aaefda8c6b4d77c782aad65bdb0aa0f76d\nSigned-off-by: Russ Knize <rknize@motorola.com>\nReviewed-on: http://gerrit.pcs.mot.com/611292\nSLTApproved: Slta Waiver <sltawvr@motorola.com>\nTested-by: Jira Key <jirakey@motorola.com>\nReviewed-by: Igor Kovalenko <igork@motorola.com>\nSubmit-Approved: Jira Key <jirakey@motorola.com>","distinct":true,"url":"https://api.github.com/repos/MCP1/android_kernel_motorola_msm8960-common/commits/98f1ba2b114b9664647c746690e7a2956e980a6a"},{"sha":"30e4be391ae8da8385b943ec795a4bf93e21d9e1","author":{"email":"2375fa63e2908bb2df59f606483a3aa92321db7a@doshaska.net","name":"nadlabak"},"message":"mmc: Add missing Motorola updates from JB release\n\nChange-Id: Icfcde3eec507814c37fb466fc8ecbf463b9bc57e","distinct":true,"url":"https://api.github.com/repos/MCP1/android_kernel_motorola_msm8960-common/commits/30e4be391ae8da8385b943ec795a4bf93e21d9e1"},{"sha":"5eef756e810b22bca8d19db8a58061accb77e2cb","author":{"email":"8892145aa7c2bcafaa8055ef206043082445675b@codeaurora.org","name":"Subhash Jadavani"},"message":"mmc: msm_sdcc: fix a type mismatch in msmsdccc_config_dma()\n\nmsmsdcc_prep_xfer() function returns a signed integer value but\ncaller function msmsdcc_config_dma() is storing this value in an unsigned\ninteger variable which is obviously not the correct thing to do.\n\nCRs-Fixed: 476578\nChange-Id: I39159e2f4f73c7f54de359cbe4faba5e902915ff\nSigned-off-by: Subhash Jadavani <subhashj@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/MCP1/android_kernel_motorola_msm8960-common/commits/5eef756e810b22bca8d19db8a58061accb77e2cb"},{"sha":"0a12a3a82f1795b3a309df11233f58db04f6f98e","author":{"email":"d09719b174b1d7232763de9bbeaca66508591b55@codeaurora.org","name":"Sujit Reddy Thumma"},"message":"mmc: msm_sdcc: Fix SPS-BAM flags while in producer mode\n\nFor read operation (writing data into system memory), the\nSDCC-BAM producer will update the EOT flags while writing\ndata done descriptors into pipe memory. It is not necessary\nthat the s/w should set EOT flag in system consumer mode as\nthat may confuse hardware.\n\nCRs-Fixed: 468046\nChange-Id: I31988fdcfaf6c9fb9c9bfc540837513ea40e125c\nSigned-off-by: Sujit Reddy Thumma <sthumma@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/MCP1/android_kernel_motorola_msm8960-common/commits/0a12a3a82f1795b3a309df11233f58db04f6f98e"},{"sha":"ab6309ec68fb3690808f6bfc07077af239a07a40","author":{"email":"bcb15852ab921cb854538b24f12d348f13e3784a@codeaurora.org","name":"Pratibhasagar V"},"message":"mmc: block: Update error handling if block data is not available\n\nWhile handling IOCTL command, if the block is not available then in the\nbail-out path it is trying to free the block data which will be executed\nagainst NULL pointer.\n\nSo, don't attempt to free the block data and only release the IOCTL\ndata.\n\nCRs-Fixed: 476581\nChange-Id: Icba46c861258d2d84b1fae5a2f5fca52ffe54255\nSigned-off-by: Pratibhasagar V <pratibha@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/MCP1/android_kernel_motorola_msm8960-common/commits/ab6309ec68fb3690808f6bfc07077af239a07a40"},{"sha":"04032784908530a4f17dbdd413f3a36792bb2c70","author":{"email":"589d3309e98dd8e96325f759fb999515c72a8edd@users.noreply.github.com","name":"Marcelo Pereira"},"message":"Merge pull request #2 from CyanogenMod/cm-12.1\n\nsync cm-12.1 20150724","distinct":true,"url":"https://api.github.com/repos/MCP1/android_kernel_motorola_msm8960-common/commits/04032784908530a4f17dbdd413f3a36792bb2c70"}]}