{"push_id":920935681,"size":1,"distinct_size":1,"ref":"refs/heads/6.0.1","head":"6f66aa1316009ebffb93da1c2913db859ad15f93","before":"003c1a32bdf03bbbd256de8aaec4ba659504b963","commits":[{"sha":"6f66aa1316009ebffb93da1c2913db859ad15f93","author":{"email":"9dca834b0a38e96a2a5a05425ca5e3d7c89ca765@codeaurora.org","name":"Ritesh Harjani"},"message":"mmc: sdhci-msm: Set MMC_CAP_WAIT_WHILE_BUSY capability\n\nFor any cmd we have a DAT line timeouts which we set in TIMEOUT_CONTROL\nregister of sdhci. For commands with busy response (R1B), cmd is followed\nby a busy period exercised by card, by pulling DAT0 line low\n(in case of CMD5). Here host controller detects this busy period and\nwaits for either busy period to finish or timeout to happen based on\nvalue set in SDHCI_TIMEOUT_CONTROL register.\n\nThus for R1B commands, host controller(sdhci) is capable of sending\ntwo interrupts. 1st is the CMD response(0th bit -  Command complete\nof Normal Interrupt Status register ) and 2nd is when the busy period has\nended(1st bit - Transfer Complete bit of Normal Interrupt Status register).\n\nIf MMC_CAP_WAIT_WHILE_BUSY is not enabled by the host controller driver\nthen core layer explictely waits for fixed amount time specified by\ns_a_timeout parameter which is generally very high when compared to\namount of time card keeps the DAT0 line low.\n\nAs sdhci-msm is capable of detecting this busy period, set\nMMC_CAP_WAIT_WHILE_BUSY capability in the host controller driver\nto avoid redundant wait period.\nOn 8952 this saves us ~110ms during mmc suspend.\n\nChange-Id: Ibb3a70575a06a5ffd1ccc3adaa96dfb3c3e22e3a\nSigned-off-by: Ritesh Harjani <riteshh@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/surdupetru/android_kernel_huawei_msm8916-caf/commits/6f66aa1316009ebffb93da1c2913db859ad15f93"}]}