From: Kang Yang <quic_kangyang@quicinc.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: <ath12k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 4/5] wifi: ath12k: remove redundant peer delete
Date: Tue, 7 May 2024 19:20:29 +0800 [thread overview]
Message-ID: <430d0e14-bc60-4872-ace7-2328532bcfc0@quicinc.com> (raw)
In-Reply-To: <171507720282.3827098.15356808712274335251.kvalo@kernel.org>
On 5/7/2024 6:20 PM, Kalle Valo wrote:
> kangyang <quic_kangyang@quicinc.com> wrote:
>
>> Firmware will create internal peer for monitor mode. For host no need to
>> do peer create and peer delete.
>>
>> So remove related code.
>>
>> 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>
>> Acked-by: Jeff Johnson <quic_jjohnson@quicinc.com>
>> Signed-off-by: Kalle Valo <quic_kvalo@quicinc.com>
>
> What about QCN9274? The commit message doesn't mention that at all. Is it safe
> to assume that QCN9274 firmware acts the same?
>
The first judgement 'ab->hw_params->vdev_start_delay' only works for
WCN7850. It won't affect QCN9274.
Sorry, i should mention.
next prev parent reply other threads:[~2024-05-07 11:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 8:15 [PATCH 0/5] prepare work for monitor mode on WCN7850 kangyang
2024-04-29 8:15 ` [PATCH 1/5] wifi: ath12k: remove unused variable monitor_flags kangyang
2024-04-30 1:49 ` Jeff Johnson
2024-05-07 10:18 ` Kalle Valo
2024-04-29 8:15 ` [PATCH 2/5] wifi: ath12k: avoid duplicated vdev stop kangyang
2024-04-30 1:51 ` Jeff Johnson
2024-04-29 8:15 ` [PATCH 3/5] wifi: ath12k: avoid duplicated vdev down kangyang
2024-04-30 1:52 ` Jeff Johnson
2024-04-29 8:15 ` [PATCH 4/5] wifi: ath12k: remove redundant peer delete kangyang
2024-04-30 1:53 ` Jeff Johnson
2024-05-07 10:20 ` Kalle Valo
2024-05-07 11:20 ` Kang Yang [this message]
2024-04-29 8:15 ` [PATCH 5/5] wifi: ath12k: remove invalid peer create logic kangyang
2024-04-30 1:55 ` Jeff Johnson
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=430d0e14-bc60-4872-ace7-2328532bcfc0@quicinc.com \
--to=quic_kangyang@quicinc.com \
--cc=ath12k@lists.infradead.org \
--cc=kvalo@kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).