From: Maya Erez <merez@codeaurora.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Maya Erez <merez@codeaurora.org>,
linux-wireless@vger.kernel.org, wil6210@qti.qualcomm.com
Subject: [PATCH v2 0/8] wil6210 patches
Date: Mon, 26 Feb 2018 20:12:10 +0200 [thread overview]
Message-ID: <1519668738-16912-1-git-send-email-merez@codeaurora.org> (raw)
Changes from v1:
Rebase patches
Support for multiple virtual interfaces (MultiVIF)
This series of patches add MultiVIF support to the wil6210 driver.
It makes it possible to start multiple interfaces where each interface
is an independent WIFI entity such as station, AP and so on.
Each virtual interface (VIF) is mapped so a separate network interface
(such as wlan0, wlan1, …) so it can also be treated separately for
routing and other network operations.
MultiVIF requires support in the FW. The FW will report whether it
supports MultiVIF and the allowed concurrency combinations. The driver
will export this information to user space and enforce it so it will
only be possible to start a combination of VIFs supported by the FW.
Initially our FW only supports multiple access points (APs) so it is
possible for example to have a secure and guest network. The code was
only validated with this scenario and we will improve the support for
other concurrency combinations with future patches, as it becomes
available in the FW.
Lior David (8):
wil6210: add wil6210_vif structure for per-VIF data
wil6210: support concurrency record in FW file
wil6210: infrastructure for multiple virtual interfaces
wil6210: add support for adding and removing virtual interfaces
wil6210: multiple VIFs support for start/stop AP
wil6210: rename p2p_wdev_mutex to vif_mutex
wil6210: multiple VIFs support for connections and data path
wil6210: add debugfs 'mids' file
drivers/net/wireless/ath/wil6210/cfg80211.c | 741 ++++++++++++++++++--------
drivers/net/wireless/ath/wil6210/debug.c | 9 +-
drivers/net/wireless/ath/wil6210/debugfs.c | 117 +++-
drivers/net/wireless/ath/wil6210/ethtool.c | 4 +-
drivers/net/wireless/ath/wil6210/fw.h | 38 +-
drivers/net/wireless/ath/wil6210/fw_inc.c | 52 +-
drivers/net/wireless/ath/wil6210/interrupt.c | 8 +-
drivers/net/wireless/ath/wil6210/main.c | 331 +++++++-----
drivers/net/wireless/ath/wil6210/netdev.c | 382 ++++++++++---
drivers/net/wireless/ath/wil6210/p2p.c | 175 +++---
drivers/net/wireless/ath/wil6210/pcie_bus.c | 57 +-
drivers/net/wireless/ath/wil6210/pm.c | 132 +++--
drivers/net/wireless/ath/wil6210/pmc.c | 8 +-
drivers/net/wireless/ath/wil6210/rx_reorder.c | 45 +-
drivers/net/wireless/ath/wil6210/txrx.c | 177 +++---
drivers/net/wireless/ath/wil6210/txrx.h | 22 +-
drivers/net/wireless/ath/wil6210/wil6210.h | 217 +++++---
drivers/net/wireless/ath/wil6210/wmi.c | 460 +++++++++++-----
18 files changed, 2081 insertions(+), 894 deletions(-)
--
1.9.1
next reply other threads:[~2018-02-26 18:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 18:12 Maya Erez [this message]
2018-02-26 18:12 ` [PATCH v2 1/8] wil6210: add wil6210_vif structure for per-VIF data Maya Erez
2018-02-27 16:52 ` [v2,1/8] " Kalle Valo
2018-02-26 18:12 ` [PATCH v2 2/8] wil6210: support concurrency record in FW file Maya Erez
2018-02-26 18:12 ` [PATCH v2 3/8] wil6210: infrastructure for multiple virtual interfaces Maya Erez
2018-02-26 18:12 ` [PATCH v2 4/8] wil6210: add support for adding and removing " Maya Erez
2018-02-26 18:12 ` [PATCH v2 5/8] wil6210: multiple VIFs support for start/stop AP Maya Erez
2018-02-26 18:12 ` [PATCH v2 6/8] wil6210: rename p2p_wdev_mutex to vif_mutex Maya Erez
2018-02-26 18:12 ` [PATCH v2 7/8] wil6210: multiple VIFs support for connections and data path Maya Erez
2018-02-26 18:12 ` [PATCH v2 8/8] wil6210: add debugfs 'mids' file Maya Erez
-- strict thread matches above, loose matches on Subject: below --
2018-01-21 9:14 [PATCH v2 0/8] wil6210 patches Maya Erez
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=1519668738-16912-1-git-send-email-merez@codeaurora.org \
--to=merez@codeaurora.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wil6210@qti.qualcomm.com \
/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).