From: Peter Oh <poh@qca.qualcomm.com>
To: <ath10k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>
Subject: [PATCH 2/3] ath10k: introduce new subtypes for proxy STA and Mesh
Date: Tue, 24 Nov 2015 09:37:34 -0800 [thread overview]
Message-ID: <1448386655-13936-3-git-send-email-poh@qca.qualcomm.com> (raw)
In-Reply-To: <1448386655-13936-1-git-send-email-poh@qca.qualcomm.com>
QCA988X firmware starting from 10.2.4.70.12-2 supports new
vdev subtypes for proxy STA and Mesh, hence add them to be used
as needed.
Signed-off-by: Peter Oh <poh@qca.qualcomm.com>
---
drivers/net/wireless/ath/ath10k/wmi.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/wireless/ath/ath10k/wmi.h b/drivers/net/wireless/ath/ath10k/wmi.h
index 0747055..d85ad78 100644
--- a/drivers/net/wireless/ath/ath10k/wmi.h
+++ b/drivers/net/wireless/ath/ath10k/wmi.h
@@ -4274,6 +4274,8 @@ enum wmi_vdev_subtype {
WMI_VDEV_SUBTYPE_P2P_DEVICE = 1,
WMI_VDEV_SUBTYPE_P2P_CLIENT = 2,
WMI_VDEV_SUBTYPE_P2P_GO = 3,
+ WMI_VDEV_SUBTYPE_PROXY_STA = 4,
+ WMI_VDEV_SUBTYPE_MESH = 5,
};
/* values for vdev_subtype */
--
1.9.1
next prev parent reply other threads:[~2015-11-24 17:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 17:37 [PATCH 0/3] ath10k: introduce Mesh support in native WiFi mode for QCA988X Peter Oh
2015-11-24 17:37 ` [PATCH 1/3] ath10k: update WMI 10.x service map Peter Oh
2015-11-24 18:08 ` kbuild test robot
2015-11-24 21:19 ` kbuild test robot
2015-11-25 1:22 ` Peter Oh
2015-11-25 10:59 ` Kalle Valo
2015-11-24 17:37 ` Peter Oh [this message]
2015-11-24 17:37 ` [PATCH 3/3] ath10k: apply Mesh subtype when Mesh interface created Peter Oh
2015-11-24 18:00 ` kbuild test robot
2015-11-24 18:20 ` kbuild test robot
2015-11-30 15:07 ` [PATCH 0/3] ath10k: introduce Mesh support in native WiFi mode for QCA988X 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=1448386655-13936-3-git-send-email-poh@qca.qualcomm.com \
--to=poh@qca.qualcomm.com \
--cc=ath10k@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).