From: Kalle Valo <kvalo@kernel.org>
To: ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: [PATCH RFC v3 0/6] wifi: ath12k: switch to using wiphy_lock()
Date: Tue, 24 Sep 2024 12:25:09 +0300 [thread overview]
Message-ID: <20240924092515.1049885-1-kvalo@kernel.org> (raw)
From: Kalle Valo <quic_kvalo@quicinc.com>
Convert all uses of struct ath12k::conf_mutex to use struct wiphy::mtx, which
is already used by mac80211, and remove conf_mutex from ath12k. This way we
have one mutex less in ath12k and simpler locking design.
I'm submitting this as RFC as I have only tested these patches and need
to investigate how this affects MLO implementation.
v3:
* new patch: wifi: ath12k: fix atomic calls in ath12k_mac_op_set_bitrate_mask()
* new patch: wifi: ath12k: ath12k_mac_op_sta_state(): clean up update_wk cancellation
* patch 3: ath12k_core_post_reconfigure_recovery(): take wiphy lock before hw_mutex to
avoid a lockdep warning
* patch 3: ath12k_sta_rc_update_wk(): remove extra wiphy_lock() calls
* patch 3: update commit message, especially remove the sparse warning which was already fixed
* rebase to ath-202409191620
v2: https://patchwork.kernel.org/project/linux-wireless/cover/20240918181042.91891-1-kvalo@kernel.org/
* rebase to ath-202409051620
* patch 1: ath12k_wow_op_suspend(): remove extra wiphy_lock()/unlock() (Baochen)
* patch 1: fix clang warnings about unused labels (Johannes)
* patch 2: s/no/now/ (Jeff)
* patch 4: ath12k_sta_rc_update_wk(): fix wiphy_priv() usage
v1: https://patchwork.kernel.org/project/linux-wireless/cover/20240821153728.2121600-1-kvalo@kernel.org/
Kalle Valo (6):
wifi: ath12k: fix atomic calls in ath12k_mac_op_set_bitrate_mask()
wifi: ath12k: convert struct ath12k_sta::update_wk to use struct
wiphy_work
wifi: ath12k: switch to using wiphy_lock() and remove ar->conf_mutex
wifi: ath12k: cleanup unneeded labels
wifi: ath12k: ath12k_mac_op_set_key(): remove exit label
wifi: ath12k: ath12k_mac_op_sta_state(): clean up update_wk
cancellation
drivers/net/wireless/ath/ath12k/core.c | 7 +-
drivers/net/wireless/ath/ath12k/core.h | 7 +-
drivers/net/wireless/ath/ath12k/debugfs.c | 4 +-
.../wireless/ath/ath12k/debugfs_htt_stats.c | 26 +-
drivers/net/wireless/ath/ath12k/mac.c | 388 +++++++-----------
drivers/net/wireless/ath/ath12k/peer.c | 6 +-
drivers/net/wireless/ath/ath12k/wow.c | 26 +-
7 files changed, 192 insertions(+), 272 deletions(-)
base-commit: d35bb26e150d7fb7434959fad9fcaeaac99906e6
--
2.39.5
next reply other threads:[~2024-09-24 9:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 9:25 Kalle Valo [this message]
2024-09-24 9:25 ` [PATCH RFC v3 1/6] wifi: ath12k: fix atomic calls in ath12k_mac_op_set_bitrate_mask() Kalle Valo
2024-09-24 9:25 ` [PATCH RFC v3 2/6] wifi: ath12k: convert struct ath12k_sta::update_wk to use struct wiphy_work Kalle Valo
2024-09-24 9:25 ` [PATCH RFC v3 3/6] wifi: ath12k: switch to using wiphy_lock() and remove ar->conf_mutex Kalle Valo
2024-10-07 14:47 ` Kalle Valo
2024-09-24 9:25 ` [PATCH RFC v3 4/6] wifi: ath12k: cleanup unneeded labels Kalle Valo
2024-09-24 9:25 ` [PATCH RFC v3 5/6] wifi: ath12k: ath12k_mac_op_set_key(): remove exit label Kalle Valo
2024-09-24 9:25 ` [PATCH RFC v3 6/6] wifi: ath12k: ath12k_mac_op_sta_state(): clean up update_wk cancellation Kalle Valo
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=20240924092515.1049885-1-kvalo@kernel.org \
--to=kvalo@kernel.org \
--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 NNTP newsgroup(s).