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 v4 0/2] wifi: ath12k: Introduce hw abstraction
Date: Thu, 18 Jan 2024 06:33:18 +0530 [thread overview]
Message-ID: <20240118010320.3918136-1-quic_periyasa@quicinc.com> (raw)
To support multi link operation (MLO), need to move from the multi wiphy
model to a single wiphy model. However, the single wiphy model allows
multiple link/radio to be exposed by the same mac80211 hw. So introduce
a new container (ath12k_hw) structure. This approach improves scalability
for future multi link operation support.
v4:
- fixed the ath12k-check warning
v3:
- Removed (struct ath12k_hw::conf_mutex) as per kalle comment
- Rebased on master branch
v2:
- Rebased on pending branch as per jeff comments
Karthikeyan Periyasamy (2):
wifi: ath12k: Refactor the mac80211 hw access from link/radio
wifi: ath12k: Introduce the container for mac80211 hw
drivers/net/wireless/ath/ath12k/core.c | 18 +-
drivers/net/wireless/ath/ath12k/core.h | 42 ++-
drivers/net/wireless/ath/ath12k/dp_mon.c | 4 +-
drivers/net/wireless/ath/ath12k/dp_rx.c | 6 +-
drivers/net/wireless/ath/ath12k/dp_tx.c | 6 +-
drivers/net/wireless/ath/ath12k/mac.c | 460 +++++++++++++++--------
drivers/net/wireless/ath/ath12k/mac.h | 4 +-
drivers/net/wireless/ath/ath12k/reg.c | 9 +-
drivers/net/wireless/ath/ath12k/wmi.c | 17 +-
9 files changed, 391 insertions(+), 175 deletions(-)
base-commit: 03a67f8046dadb966950a0a6acbac2839cddfeb1
--
2.34.1
next reply other threads:[~2024-01-18 1:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 1:03 Karthikeyan Periyasamy [this message]
2024-01-18 1:03 ` [PATCH v4 1/2] wifi: ath12k: Refactor the mac80211 hw access from link/radio Karthikeyan Periyasamy
2024-01-18 16:02 ` Jeff Johnson
2024-01-19 17:39 ` Kalle Valo
2024-01-18 1:03 ` [PATCH v4 2/2] wifi: ath12k: Introduce the container for mac80211 hw Karthikeyan Periyasamy
2024-01-18 16:03 ` 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=20240118010320.3918136-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).