[PATCH 3/3] ath11k: monitor mode clean up to use separate APIs
Kalle Valo
kvalo at codeaurora.org
Thu Sep 16 02:35:45 PDT 2021
Jouni Malinen <jouni at codeaurora.org> writes:
> From: Seevalamuthu Mariappan <seevalam at codeaurora.org>
>
> If monitor interface is enabled in co-exist mode, only local traffic are
> captured. It's caused by missing monitor vdev in co-exist mode. So,
> monitor mode clean up is done with separate Monitor APIs. For this,
> introduce monitor_started and monitor_vdev_created boolean flags.
>
> Tested-on: IPQ8074 hw2.0 AHB WLAN.HK.2.4.0.1-01725-QCAHKSWPL_SILICONZ-1
Seevalamuthu, in upstream IPQ8074 doesn't even support monitor mode:
static const struct ath11k_hw_params ath11k_hw_params[] = {
{
.hw_rev = ATH11K_HW_IPQ8074,
.name = "ipq8074 hw2.0",
...
.interface_modes = BIT(NL80211_IFTYPE_STATION) |
BIT(NL80211_IFTYPE_AP) |
BIT(NL80211_IFTYPE_MESH_POINT),
So I wonder how did you test this? Is this something which is only
tested on ancient QSDK kernels and not with upstream kernels?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
More information about the ath11k
mailing list