From: Kalle Valo <kvalo@kernel.org>
To: ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: [PATCH RFC v2 0/4] wifi: ath12k: switch to using wiphy_lock()
Date: Wed, 18 Sep 2024 21:10:38 +0300 [thread overview]
Message-ID: <20240918181042.91891-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.
v2:
* 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 (4):
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: convert struct ath12k_sta::update_wk to use struct
wiphy_work
drivers/net/wireless/ath/ath12k/core.c | 6 +-
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 | 363 +++++++-----------
drivers/net/wireless/ath/ath12k/peer.c | 6 +-
drivers/net/wireless/ath/ath12k/wow.c | 26 +-
7 files changed, 183 insertions(+), 255 deletions(-)
base-commit: 903aaf66edc97dd5b9e3118d19677291051a9c40
--
2.39.5
next reply other threads:[~2024-09-18 18:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 18:10 Kalle Valo [this message]
2024-09-18 18:10 ` [PATCH RFC v2 1/4] wifi: ath12k: switch to using wiphy_lock() and remove ar->conf_mutex Kalle Valo
2024-09-19 2:43 ` Baochen Qiang
2024-09-24 8:57 ` Kalle Valo
2024-09-24 10:03 ` Kalle Valo
2024-09-19 7:06 ` Johannes Berg
2024-09-24 9:11 ` Kalle Valo
2024-09-24 9:15 ` Johannes Berg
2024-09-18 18:10 ` [PATCH RFC v2 2/4] wifi: ath12k: cleanup unneeded labels Kalle Valo
2024-09-18 18:10 ` [PATCH RFC v2 3/4] wifi: ath12k: ath12k_mac_op_set_key(): remove exit label Kalle Valo
2024-09-18 18:10 ` [PATCH RFC v2 4/4] wifi: ath12k: convert struct ath12k_sta::update_wk to use struct wiphy_work Kalle Valo
2024-09-19 3:01 ` Baochen Qiang
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=20240918181042.91891-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