From: Seungwon Jeon <tgih....@samsung.com>

There is no need to check the version to clear
the interrupt status. And the order is changed
prior to actual handling.

Signed-off-by: Seungwon Jeon <tgih....@samsung.com>
Tested-by: Maya Erez <me...@codeaurora.org>
Signed-off-by: Santosh Y <santos...@gmail.com>

diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
index 1f1e085..2e02483 100644
--- a/drivers/scsi/ufs/ufshcd.c
+++ b/drivers/scsi/ufs/ufshcd.c
@@ -1324,11 +1324,8 @@ static irqreturn_t ufshcd_intr(int irq, void *__hba)
        intr_status = ufshcd_readl(hba, REG_INTERRUPT_STATUS);
 
        if (intr_status) {
+               ufshcd_writel(hba, intr_status, REG_INTERRUPT_STATUS);
                ufshcd_sl_intr(hba, intr_status);
-
-               /* If UFSHCI 1.0 then clear interrupt status register */
-               if (hba->ufs_version == UFSHCI_VERSION_10)
-                       ufshcd_writel(hba, intr_status, REG_INTERRUPT_STATUS);
                retval = IRQ_HANDLED;
        }
        spin_unlock(hba->host->host_lock);
-- 
1.8.3.1

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to