public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
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: Fri, 6 Dec 2024 10:24:32 +0800	[thread overview]
Message-ID: <0f24e115-e76d-4c8a-8a1b-591a157ee78e@quicinc.com> (raw)
In-Reply-To: <20241205110704.232725-1-jtornosm@redhat.com>



On 12/5/2024 7:07 PM, Jose Ignacio Tornos Martinez wrote:
>> But I see your interfaces all be added with managed, right?
> Yes
> 
My point is that you can try setup with ap type interface, now 
combination limits not allow up 3 inferfaces with managed interface.
>> Test steps:
>> ...
> Ok, I am using a bridge with the AP interfaces in addition but it is
> the same.
> Indeed I have tested in the same way as you too (even using your
> hostapd.conf with the suitable name for the interfaces).
> So I have started to debug (current upstream linux +
> https://lore.kernel.org/all/20241127022742.4016870-1-quic_yuzha@quicinc.com/ +
> dump_stack() in ath11k_mac_op_add_interface, enabling ath11k_dbg),
> let me show you this:
> [    5.703295] ath11k_pci 0000:01:00.0: vdev a2:d8:da:c5:7b:79 created, vdev_id 0
> [    5.703304] CPU: 4 UID: 0 PID: 945 Comm: NetworkManager Tainted: G        W          6.12.0+ #104
> [    5.703315] Tainted: [W]=WARN
> [    5.703317] Hardware name: ASUS System Product Name/PRIME B660-PLUS D4, BIOS 1620 08/12/2022
> [    5.703320] Call Trace:
> [    5.703325]  <TASK>
> [    5.703330]  dump_stack_lvl+0x5d/0x80
> [    5.703344]  ath11k_mac_op_add_interface.cold+0x4ed/0xa92 [ath11k]
> [    5.703399]  drv_add_interface+0x4f/0x230 [mac80211]
> [    5.703512]  ieee80211_do_open+0x4b3/0x770 [mac80211]
> [    5.703669]  ieee80211_open+0x8a/0x90 [mac80211]
> ...
> [    5.804755] ath11k_pci 0000:01:00.0: vdev c8:94:02:b5:fe:fb created, vdev_id 1
> [    5.804759] CPU: 1 UID: 0 PID: 1011 Comm: wpa_supplicant Tainted: G        W          6.12.0+ #104
> [    5.804763] Tainted: [W]=WARN
> [    5.804765] Hardware name: ASUS System Product Name/PRIME B660-PLUS D4, BIOS 1620 08/12/2022
> [    5.804766] Call Trace:
> [    5.804770]  <TASK>
> [    5.804773]  dump_stack_lvl+0x5d/0x80
> [    5.804783]  ath11k_mac_op_add_interface.cold+0x4ed/0xa92 [ath11k]
> [    5.804809]  drv_add_interface+0x4f/0x230 [mac80211]
> [    5.804868]  ieee80211_do_open+0x4b3/0x770 [mac80211]
> [    5.804934]  nl80211_start_p2p_device+0x8b/0x160 [cfg80211]
> ...
> So, since the normal sta interface and p2p interface are initialized,
> with your proposed interface combination, only one AP interface can be
> added for me (vdev limit is 3).
> I like your idea to have a common interface combination set for everything,
> but I think it is not possible here.
> My patch with the new parameter at least allow to select what to do, dual
> stations support or APs support for all the cases.
> 
> Thanks
> 
> Best regards
> Jose Ignacio
> 


  reply	other threads:[~2024-12-06  2:24 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-02  9:18 [PATCH] wifi: ath11k: allow APs combination when dual stations are supported 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)
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) [this message]
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=0f24e115-e76d-4c8a-8a1b-591a157ee78e@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