From: Kalle Valo <kvalo@kernel.org>
To: Aloka Dixit <quic_alokad@quicinc.com>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3 4/7] wifi: ath11k: MBSSID parameter configuration in AP mode
Date: Sat, 29 Apr 2023 08:37:40 +0300 [thread overview]
Message-ID: <87leibqme3.fsf@kernel.org> (raw)
In-Reply-To: <20230405221648.17950-5-quic_alokad@quicinc.com> (Aloka Dixit's message of "Wed, 5 Apr 2023 15:16:45 -0700")
Aloka Dixit <quic_alokad@quicinc.com> writes:
> Include MBSSID parameters in WMI vdev up operation.
>
> Tested-on : IPQ8074 hw2.0 AHB WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1
> Signed-off-by: Aloka Dixit <quic_alokad@quicinc.com>
> Co-developed-by: John Crispin <john@phrozen.org>
> Signed-off-by: John Crispin <john@phrozen.org>
> ---
[...]
> @@ -7153,8 +7161,13 @@ ath11k_mac_update_vif_chan(struct ath11k *ar,
> ath11k_warn(ab, "failed to update bcn tmpl during csa: %d\n",
> ret);
>
> + if (arvif->vif->mbssid_tx_vif)
> + tx_arvif = (struct ath11k_vif *)arvif->vif->mbssid_tx_vif->drv_priv;
This had a warning:
drivers/net/wireless/ath/ath11k/mac.c:7200: line length of 92 exceeds 90 columns
In the pending branch I fixed it like this:
--- a/drivers/net/wireless/ath/ath11k/mac.c
+++ b/drivers/net/wireless/ath/ath11k/mac.c
@@ -7143,6 +7143,7 @@ ath11k_mac_update_vif_chan(struct ath11k *ar,
{
struct ath11k_base *ab = ar->ab;
struct ath11k_vif *arvif, *tx_arvif = NULL;
+ struct ieee80211_vif *mbssid_tx_vif;
int ret;
int i;
bool monitor_vif = false;
@@ -7196,8 +7197,10 @@ ath11k_mac_update_vif_chan(struct ath11k *ar,
ath11k_warn(ab, "failed to update bcn tmpl during csa: %d\n",
ret);
- if (arvif->vif->mbssid_tx_vif)
- tx_arvif = (struct ath11k_vif *)arvif->vif->mbssid_tx_vif->drv_priv;
+ mbssid_tx_vif = arvif->vif->mbssid_tx_vif;
+ if (mbssid_tx_vif)
+ tx_arvif = (struct ath11k_vif *)mbssid_tx_vif->drv_priv;
+
ret = ath11k_wmi_vdev_up(arvif->ar, arvif->vdev_id, arvif->aid,
arvif->bssid,
tx_arvif ? tx_arvif->bssid : NULL,
Link to the commit:
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=pending&id=c884238009e778a0c8202a5eb0a7f68b13200bde
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-04-29 5:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 22:16 [PATCH v3 0/7] v3: ath11k: MBSSID and EMA support in AP mode Aloka Dixit
2023-04-05 22:16 ` [PATCH v3 1/7] wifi: ath11k: driver settings for MBSSID and EMA Aloka Dixit
2023-05-09 16:59 ` Kalle Valo
2023-04-05 22:16 ` [PATCH v3 2/7] wifi: ath11k: MBSSID configuration during vdev create/start Aloka Dixit
2023-04-05 22:16 ` [PATCH v3 3/7] wifi: ath11k: rename MBSSID fields in wmi_vdev_up_cmd Aloka Dixit
2023-04-05 22:16 ` [PATCH v3 4/7] wifi: ath11k: MBSSID parameter configuration in AP mode Aloka Dixit
2023-04-29 5:37 ` Kalle Valo [this message]
2023-05-01 17:41 ` Aloka Dixit
2023-05-05 13:28 ` Kalle Valo
2023-04-05 22:16 ` [PATCH v3 5/7] wifi: ath11k: refactor vif parameter configurations Aloka Dixit
2023-04-05 22:16 ` [PATCH v3 6/7] wifi: ath11k: MBSSID beacon support Aloka Dixit
2023-04-05 22:16 ` [PATCH v3 7/7] wifi: ath11k: EMA " Aloka Dixit
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=87leibqme3.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_alokad@quicinc.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).