ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mihai Moldovan <ionic@ionic.de>
To: ath11k@lists.infradead.org
Subject: Re: [PATCH v2] wifi: ath11k: support DBS and DFS compatibility
Date: Tue, 26 Nov 2024 07:09:55 +0100	[thread overview]
Message-ID: <90c806db-9d75-4c25-88f5-252da80b5d40@ionic.de> (raw)
In-Reply-To: <20241125100508.3458594-1-quic_yuzha@quicinc.com>


[-- Attachment #1.1: Type: text/plain, Size: 2541 bytes --]

* On 11/25/24 11:05, Yu Zhang(Yuriy) wrote:
> Add a ieee80211_iface_combination to support DBS and DFS compatibility,
> one combination can support DFS(same with non dual sta), another
> combination can support DBS. When running different scenarios that will
> use different ieee80211_iface_combination due to mac80211 will go through
> all of possible interface combinations.

Are DFS and DBS mutually exclusive features? I can imagine that ISM clashes with 
DBS, but wonder if this is a hardware limitation, a firmware limitation or 
merely an implementation limitation so far that might eventually be lifted.


> The chips affected are:
> 
>   QCA6390 hw2.0

Tested-by: Mihai Moldovan <ionic@ionic.de>
Tested-on: QCA6390 hw2.0 PCI WLAN.HST.1.0.1-05266-QCAHSTSWPLZ_V2_TO_X86-1


These were the tested configurations:

   - 5 GHz on DFS channel:

         Interface wifiax
                 ifindex 6
                 wdev 0x1
                 addr 20:57:9e:2d:04:1e
                 ssid WRTKA05
                 type AP
                 channel 100 (5500 MHz), width: 80 MHz, center1: 5530 MHz
                 txpower 20.00 dBm
                 multicast TXQ:
                         qsz-byt qsz-pkt flows   drops   marks   overlmt hashcol 
tx-bytes        tx-packets
                         0       0       454     0       0       0       0 
61456           454

   - 5 GHz on non-DFS channel + 2.4 GHz (DBS):

         Interface wifiax24
                 ifindex 7
                 wdev 0x2
                 addr 22:57:9e:2d:04:1e
                 ssid WRTKA06-Tasmota
                 type AP
                 channel 7 (2442 MHz), width: 40 MHz, center1: 2452 MHz
                 txpower 20.00 dBm
                 multicast TXQ:
                         qsz-byt qsz-pkt flows   drops   marks   overlmt hashcol 
tx-bytes        tx-packets
                         0       0       61      0       0       0       0 
8562            61
         Interface wifiax
                 ifindex 6
                 wdev 0x1
                 addr 20:57:9e:2d:04:1e
                 ssid WRTKA05
                 type AP
                 channel 40 (5200 MHz), width: 80 MHz, center1: 5210 MHz
                 txpower 20.00 dBm
                 multicast TXQ:
                         qsz-byt qsz-pkt flows   drops   marks   overlmt hashcol 
tx-bytes        tx-packets
                         0       0       69      0       0       0       0 
10032           69



Mihai

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2024-11-26  6:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 10:05 [PATCH v2] wifi: ath11k: support DBS and DFS compatibility Yu Zhang(Yuriy)
2024-11-26  6:09 ` Mihai Moldovan [this message]
2024-11-26  8:14   ` Yu Zhang (Yuriy)

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=90c806db-9d75-4c25-88f5-252da80b5d40@ionic.de \
    --to=ionic@ionic.de \
    --cc=ath11k@lists.infradead.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