From: Kalle Valo <kvalo@kernel.org>
To: Kang Yang <quic_kangyang@quicinc.com>
Cc: <ath12k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
<quic_kangyang@quicinc.com>
Subject: Re: [PATCH v2] wifi: ath12k: dynamically update peer puncturing bitmap for STA
Date: Tue, 16 Apr 2024 07:19:24 +0000 (UTC) [thread overview]
Message-ID: <171325196269.4097708.17420156398205225314.kvalo@kernel.org> (raw)
In-Reply-To: <20240408083047.22548-1-quic_kangyang@quicinc.com>
Kang Yang <quic_kangyang@quicinc.com> wrote:
> Every time EHT Operation element changed, mac80211 will parse it and
> extract the valid puncturing bitmap according to the bandwidth.
>
> Current driver only update puncturing bitmap to firmware as vdev
> parameter. Which can only meet the needs of AP. But STA will also use
> it as peer parameter. If only update as vdev parameter, might cause
> firmware crash. QCN9274 is the same.
>
> So update bandwidth and puncturing bitmap as peer parameters once they
> changed for STA. Then send them to the firmware by WMI event.
>
> Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3
>
> Signed-off-by: Kang Yang <quic_kangyang@quicinc.com>
> Signed-off-by: Kalle Valo <quic_kvalo@quicinc.com>
Patch applied to ath-next branch of ath.git, thanks.
0531825408ce wifi: ath12k: dynamically update peer puncturing bitmap for STA
--
https://patchwork.kernel.org/project/linux-wireless/patch/20240408083047.22548-1-quic_kangyang@quicinc.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2024-04-16 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 8:30 [PATCH v2] wifi: ath12k: dynamically update peer puncturing bitmap for STA Kang Yang
2024-04-16 7:19 ` Kalle Valo [this message]
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=171325196269.4097708.17420156398205225314.kvalo@kernel.org \
--to=kvalo@kernel.org \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_kangyang@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 read-only IMAP folder(s) and NNTP newsgroup(s).