[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20181013005504.46399-4-briannorris@chromium.org>
Date: Fri, 12 Oct 2018 17:55:04 -0700
From: Brian Norris <briannorris@...omium.org>
To: Kalle Valo <kvalo@....qualcomm.com>
Cc: ath10k@...ts.infradead.org, linux-wireless@...r.kernel.org,
Govind Singh <govinds@...eaurora.org>,
Doug Anderson <dianders@...omium.org>,
<linux-kernel@...r.kernel.org>,
Brian Norris <briannorris@...omium.org>
Subject: [PATCH 4/4] ath10k: snoc: fix unbalanced clock error handling
Similar to regulator error handling, we should only start tearing down
the 'i - 1' clock when clock 'i' fails to enable. Otherwise, we might
end up with an unbalanced clock, where we never successfully enabled the
clock, but we try to disable it anyway.
Signed-off-by: Brian Norris <briannorris@...omium.org>
---
drivers/net/wireless/ath/ath10k/snoc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ath/ath10k/snoc.c b/drivers/net/wireless/ath/ath10k/snoc.c
index 5a8e87339df2..a835599a8d55 100644
--- a/drivers/net/wireless/ath/ath10k/snoc.c
+++ b/drivers/net/wireless/ath/ath10k/snoc.c
@@ -1470,7 +1470,7 @@ static int ath10k_snoc_clk_init(struct ath10k *ar)
return 0;
err_clock_config:
- for (; i >= 0; i--) {
+ for (i = i - 1; i >= 0; i--) {
clk_info = &ar_snoc->clk[i];
if (!clk_info->handle)
--
2.19.1.331.ge82ca0e54c-goog
Powered by blists - more mailing lists