From: Wen Gong <wgong@codeaurora.org>
To: ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: [PATCH v3 1/2] ath10k: add refcount for ath10k_core_restart
Date: Tue, 31 Dec 2019 17:28:05 +0800 [thread overview]
Message-ID: <20191231092806.6247-2-wgong@codeaurora.org> (raw)
In-Reply-To: <20191231092806.6247-1-wgong@codeaurora.org>
When it has more than one restart_work queued meanwhile, the 2nd
restart_work is very esay to break the 1st restart work and lead
recovery fail.
Add a ref count to allow only one restart work running untill
device successfully recovered.
Tested with QCA6174 SDIO with firmware WLAN.RMH.4.4.1-00029.
Signed-off-by: Wen Gong <wgong@codeaurora.org>
---
drivers/net/wireless/ath/ath10k/core.c | 8 ++++++++
drivers/net/wireless/ath/ath10k/core.h | 2 ++
drivers/net/wireless/ath/ath10k/mac.c | 1 +
3 files changed, 11 insertions(+)
diff --git a/drivers/net/wireless/ath/ath10k/core.c b/drivers/net/wireless/ath/ath10k/core.c
index 91f131b87efc..9439e575ec63 100644
--- a/drivers/net/wireless/ath/ath10k/core.c
+++ b/drivers/net/wireless/ath/ath10k/core.c
@@ -2199,6 +2199,14 @@ static void ath10k_core_restart(struct work_struct *work)
{
struct ath10k *ar = container_of(work, struct ath10k, restart_work);
int ret;
+ int restart_count;
+
+ restart_count = atomic_add_return(1, &ar->restart_count);
+ if (restart_count > 1) {
+ ath10k_warn(ar, "can not restart, count: %d\n", restart_count);
+ atomic_dec(&ar->restart_count);
+ return;
+ }
set_bit(ATH10K_FLAG_CRASH_FLUSH, &ar->dev_flags);
diff --git a/drivers/net/wireless/ath/ath10k/core.h b/drivers/net/wireless/ath/ath10k/core.h
index e57b2e7235e3..810c99f2dc0e 100644
--- a/drivers/net/wireless/ath/ath10k/core.h
+++ b/drivers/net/wireless/ath/ath10k/core.h
@@ -982,6 +982,8 @@ struct ath10k {
/* protected by conf_mutex */
u8 ps_state_enable;
+ atomic_t restart_count;
+
bool nlo_enabled;
bool p2p;
diff --git a/drivers/net/wireless/ath/ath10k/mac.c b/drivers/net/wireless/ath/ath10k/mac.c
index 3856edba7915..bc1574145e66 100644
--- a/drivers/net/wireless/ath/ath10k/mac.c
+++ b/drivers/net/wireless/ath/ath10k/mac.c
@@ -7208,6 +7208,7 @@ static void ath10k_reconfig_complete(struct ieee80211_hw *hw,
ath10k_info(ar, "device successfully recovered\n");
ar->state = ATH10K_STATE_ON;
ieee80211_wake_queues(ar->hw);
+ atomic_dec(&ar->restart_count);
}
mutex_unlock(&ar->conf_mutex);
--
2.23.0
next prev parent reply other threads:[~2019-12-31 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-31 9:28 [PATCH v3 0/2] start recovery process when payload length overflow for sdio Wen Gong
2019-12-31 9:28 ` Wen Gong [this message]
2019-12-31 9:28 ` [PATCH v3 2/2] ath10k: start recovery process when payload length exceeds max htc length " Wen Gong
2020-01-08 3:23 ` [PATCH v3 0/2] start recovery process when payload length overflow " Wen Gong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191231092806.6247-2-wgong@codeaurora.org \
--to=wgong@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).