From: "Yu Zhang (Yuriy)" <quic_yuzha@quicinc.com>
To: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
Cc: <ath11k@lists.infradead.org>, <jjohnson@kernel.org>,
<kvalo@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-wireless@vger.kernel.org>, <quic_cjhuang@quicinc.com>,
<vbenes@redhat.com>
Subject: Re: [PATCH] wifi: ath11k: allow APs combination when dual stations are supported
Date: Tue, 3 Dec 2024 18:48:58 +0800 [thread overview]
Message-ID: <99359cc4-2279-4a8a-80a1-d5475fd5208d@quicinc.com> (raw)
In-Reply-To: <20241203094820.106225-1-jtornosm@redhat.com>
On 12/3/2024 5:48 PM, Jose Ignacio Tornos Martinez wrote:
>> Which chip do you use?
> Since I am not totally sure about the useful information, let me show you
> the kernel logs:
> $ dmesg | grep ath11k
> [ 3.659388] ath11k_pci 0000:01:00.0: BAR 0 [mem 0x84200000-0x843fffff 64bit]: assigned
> [ 3.659405] ath11k_pci 0000:01:00.0: enabling device (0000 -> 0002)
> [ 3.659649] ath11k_pci 0000:01:00.0: MSI vectors: 32
> [ 3.659653] ath11k_pci 0000:01:00.0: wcn6855 hw2.1
> [ 4.871571] ath11k_pci 0000:01:00.0: chip_id 0x2 chip_family 0xb board_id 0xff soc_id 0x400c0210
> [ 4.871586] ath11k_pci 0000:01:00.0: fw_version 0x11088c35 fw_build_timestamp 2024-04-17 08:34 fw_build_id WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.41
> [ 5.241485] ath11k_pci 0000:01:00.0 wlp1s0: renamed from wlan0
>
yes, you also use wcn6855 hw2.1.
> If I try to setup 2 APs with your interface combination I get this:
> # iw list | grep -A6 "valid interface combinations:"
> valid interface combinations:
> * #{ managed } <= 2, #{ AP, P2P-client, P2P-GO } <= 16, #{ P2P-device } <= 1,
> total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 80+80 MHz, 160 MHz }
>
> * #{ managed } <= 2, #{ AP, P2P-client, P2P-GO } <= 16, #{ P2P-device } <= 1,
> total <= 3, #channels <= 2, STA/AP BI must match
> HT Capability overrides:
2 combinations are to support DBS and DFS.
Combinations is correct. channels=2, max interfaces=3.
And you want setup sta + sap + sap, right?
When up the second sap will meet error? Could you pls share the error logs?
I'm not very sure if you add all interface with managed type, and do
"ifconfig xxx up" before running hostapd.
You can try add second and third interface with
"iw dev xx interface add xx type __ap".
> # iw dev
> phy#0
> Interface wlp1s0_1
> ifindex 6
> wdev 0x4
> addr a2:42:d2:1e:89:a3
> type managed
> txpower 16.00 dBm
> multicast TXQ:
> qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
> 0 0 0 0 0 0 0 0 0
> Interface wlp1s0_0
> ifindex 5
> wdev 0x3
> addr 52:e9:be:33:6a:61
> ssid test-qe-wpa2-psk
> type AP
> channel 13 (2472 MHz), width: 20 MHz, center1: 2472 MHz
> txpower 14.00 dBm
> multicast TXQ:
> qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
> 0 0 0 0 0 0 0 0 0
> Interface wlp1s0
> ifindex 3
> wdev 0x1
> addr c8:94:02:b5:fe:fb
> type managed
> txpower 16.00 dBm
> multicast TXQ:
> qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
> 0 0 0 0 0 0 0 0 0
> Or even this with no AP up:
> # iw dev
> phy#0
> Interface wlp1s0_1
> ifindex 6
> wdev 0x4
> addr ca:e5:84:22:10:ec
> type managed
> txpower 16.00 dBm
> multicast TXQ:
> qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
> 0 0 0 0 0 0 0 0 0
> Interface wlp1s0_0
> ifindex 5
> wdev 0x3
> addr 9e:4e:c5:ea:4c:e9
> type AP
> txpower 16.00 dBm
> multicast TXQ:
> qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
> 0 0 0 0 0 0 0 0 0
> Interface wlp1s0
> ifindex 3
> wdev 0x1
> addr c8:94:02:b5:fe:fb
> type managed
> txpower 16.00 dBm
> multicast TXQ:
> qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
> 0 0 0 0 0 0 0 0 0
>
> If I use the parameter to ignore the feature and configure the interface combination as before:
> # iw list | grep -A4 "valid interface combinations:"
> valid interface combinations:
> * #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 16, #{ P2P-device } <= 1,
> total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }
>
> HT Capability overrides:
> # iw dev
> phy#1
> Interface wlp1s0_1
> ifindex 7
> wdev 0x100000004
> addr 82:90:89:90:c1:37
> ssid test-qe-wpa3-psk
> type AP
> channel 13 (2472 MHz), width: 20 MHz, center1: 2472 MHz
> txpower 16.00 dBm
> multicast TXQ:
> qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
> 0 0 0 0 0 0 0 0 0
> Interface wlp1s0_0
> ifindex 6
> wdev 0x100000003
> addr 6a:ef:d0:db:10:f0
> ssid test-qe-wpa2-psk
> type AP
> channel 13 (2472 MHz), width: 20 MHz, center1: 2472 MHz
> txpower 16.00 dBm
> multicast TXQ:
> qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
> 0 0 0 0 0 0 0 0 0
> Interface wlp1s0
> ifindex 4
> wdev 0x100000001
> addr c8:94:02:b5:fe:fb
> type managed
> txpower 16.00 dBm
> multicast TXQ:
> qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
> 0 0 0 0 0 0 0 0 0
>
> Thanks
>
> Best regards
> Jose Ignacio
>
next prev parent reply other threads:[~2024-12-03 10:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 9:18 Jose Ignacio Tornos Martinez
2024-12-03 1:54 ` Yu Zhang (Yuriy)
2024-12-03 8:04 ` Jose Ignacio Tornos Martinez
2024-12-03 8:28 ` Yu Zhang (Yuriy)
2024-12-03 9:48 ` Jose Ignacio Tornos Martinez
2024-12-03 10:48 ` Yu Zhang (Yuriy) [this message]
2024-12-03 16:33 ` Jose Ignacio Tornos Martinez
2024-12-04 3:21 ` Yu Zhang (Yuriy)
2024-12-04 7:51 ` Jose Ignacio Tornos Martinez
2024-12-04 8:30 ` Jose Ignacio Tornos Martinez
2024-12-04 9:18 ` Yu Zhang (Yuriy)
2024-12-05 11:07 ` Jose Ignacio Tornos Martinez
2024-12-06 2:24 ` Yu Zhang (Yuriy)
2024-12-08 12:13 ` Jose Ignacio Tornos Martinez
2024-12-09 2:29 ` Yu Zhang (Yuriy)
2024-12-09 8:03 ` Jose Ignacio Tornos Martinez
2024-12-09 8:33 ` Yu Zhang (Yuriy)
2024-12-10 8:44 ` Jose Ignacio Tornos Martinez
2024-12-11 2:10 ` Yu Zhang (Yuriy)
2024-12-11 17:41 ` Jose Ignacio Tornos Martinez
2025-01-14 18:34 ` Jose Ignacio Tornos Martinez
2025-01-15 8:59 ` Yu Zhang (Yuriy)
2025-01-15 9:46 ` Jose Ignacio Tornos Martinez
2025-01-15 10:48 ` Yu Zhang (Yuriy)
2025-01-15 11:06 ` Jose Ignacio Tornos Martinez
2025-01-15 11:20 ` Yu Zhang (Yuriy)
2025-01-15 11:55 ` Jose Ignacio Tornos Martinez
2025-01-15 12:04 ` Yu Zhang (Yuriy)
2025-01-15 13:03 ` Jose Ignacio Tornos Martinez
2025-01-16 0:31 ` Jeff Johnson
2025-02-06 7:46 ` Yu Zhang (Yuriy)
2025-02-06 20:20 ` Jeff Johnson
2025-02-07 2:01 ` Yu Zhang (Yuriy)
2025-04-02 12:23 ` Yu Zhang (Yuriy)
2024-12-09 11:23 ` Janusz Dziedzic
2024-12-10 2:32 ` 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=99359cc4-2279-4a8a-80a1-d5475fd5208d@quicinc.com \
--to=quic_yuzha@quicinc.com \
--cc=ath11k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=jtornosm@redhat.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_cjhuang@quicinc.com \
--cc=vbenes@redhat.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
all inboxes | Powered by JetHome®