From 376a0081590defc3ba857643812add02d3cd383c Mon Sep 17 00:00:00 2001
From: Yuanfang Zhang <zhangyuanfang@codeaurora.org>
Date: Thu, 28 May 2020 23:23:49 +0800
Subject: [PATCH] memory_dump: resolve the issue of configuring core_reg_numer

When the new core_reg_number value is the same as previous value,
writing to core_reg_number node cannot exit normally, this
change resolve this issue.

Change-Id: I6cbb301fc77a630aa9f01a68341c9510fdbd5c0f
Signed-off-by: Yuanfang Zhang <zhangyuanfang@codeaurora.org>
---
 drivers/soc/qcom/memory_dump_v2.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/soc/qcom/memory_dump_v2.c b/drivers/soc/qcom/memory_dump_v2.c
index e997ae357602..a56362923111 100644
--- a/drivers/soc/qcom/memory_dump_v2.c
+++ b/drivers/soc/qcom/memory_dump_v2.c
@@ -168,8 +168,8 @@ static ssize_t core_reg_num_store(struct device *dev,
 		goto err;
 	}
 	if (val == cpudata->core_reg_num) {
-		ret = 0;
-		goto err;
+		mutex_unlock(&cpudata->mutex);
+		return size;
 	}
 
 	mutex_unlock(&cpudata->mutex);