From: Karthikeyan Periyasamy <quic_periyasa@quicinc.com>
To: <ath12k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>,
Karthikeyan Periyasamy <quic_periyasa@quicinc.com>
Subject: [PATCH v3 0/3] wifi: ath12k: Refactor the hardware recovery procedures
Date: Thu, 25 Apr 2024 14:33:04 +0530 [thread overview]
Message-ID: <20240425090307.3233434-1-quic_periyasa@quicinc.com> (raw)
Currently, hardware recovery procedure supports multi wiphy model. However,
to support single wiphy model, we need to refactor the hardware recovery
procedure. This patchset allows the logic to work both multi wiphy models
and future single wiphy models.
v3:
wifi: ath12k: Refactor the hardware recovery procedure
* Removed unnecessary conditional check
wifi: ath12k: Add lock to protect the hardware state
* Introduce auto guard mutex
v2:
- Rebased to ToT
- Renamed the lock name as per the kalle comments
Karthikeyan Periyasamy (3):
wifi: ath12k: Refactor the hardware recovery procedure
wifi: ath12k: Refactor the hardware state
wifi: ath12k: Add lock to protect the hardware state
drivers/net/wireless/ath/ath12k/core.c | 98 ++++++++++++++------------
drivers/net/wireless/ath/ath12k/core.h | 28 +++++---
drivers/net/wireless/ath/ath12k/mac.c | 88 +++++++++++++++--------
drivers/net/wireless/ath/ath12k/reg.c | 19 ++---
4 files changed, 141 insertions(+), 92 deletions(-)
base-commit: 326f8f68f28b0b831233acfabffb486a5b0f4717
--
2.34.1
next reply other threads:[~2024-04-25 9:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 9:03 Karthikeyan Periyasamy [this message]
2024-04-25 9:03 ` [PATCH v3 1/3] wifi: ath12k: Refactor the hardware recovery procedure Karthikeyan Periyasamy
2024-04-25 21:09 ` Jeff Johnson
2024-05-03 13:12 ` Kalle Valo
2024-04-25 9:03 ` [PATCH v3 2/3] wifi: ath12k: Refactor the hardware state Karthikeyan Periyasamy
2024-04-25 21:11 ` Jeff Johnson
2024-04-25 9:03 ` [PATCH v3 3/3] wifi: ath12k: Add lock to protect " Karthikeyan Periyasamy
2024-04-25 21:16 ` Jeff Johnson
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=20240425090307.3233434-1-quic_periyasa@quicinc.com \
--to=quic_periyasa@quicinc.com \
--cc=ath12k@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 read-only IMAP folder(s) and NNTP newsgroup(s).