From: Ben Greear <greearb@candelatech.com>
To: Vasanthakumar Thiagarajan
<vasanthakumar.thiagarajan@oss.qualcomm.com>,
Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
ath12k@lists.infradead.org
Subject: Re: ath12k pcie radios with MLO support?
Date: Wed, 12 Nov 2025 07:36:15 -0800 [thread overview]
Message-ID: <3f43654b-3fca-4020-8393-d028991edba1@candelatech.com> (raw)
In-Reply-To: <4648e6df-08da-9d7a-63e2-d2b850ccabb4@oss.qualcomm.com>
On 11/11/25 21:15, Vasanthakumar Thiagarajan wrote:
>
>
> On 11/12/2025 7:10 AM, Ben Greear wrote:
>> On 11/11/25 17:29, Jeff Johnson wrote:
>>> On 11/11/2025 7:27 AM, Ben Greear wrote:
>>>> Hello,
>>>>
>>>> Are there any current radios + software available where one can put
>>>> ath12k radios in (mini)pcie slots or similar and use those in x86-64
>>>> chassis and provide tri-band MLO?
>>>>
>>>> Last I looked, Compex had some dual-band radios and maybe single-band
>>>> 6ghz, but I am not sure those can be combined into a tri-band MLO solution?
>>>
>>> Most of the Compex modules use the AP-centric QCN chipsets.
>>> For your use case look for something using the WCN chipset.
>>>
>>> Something like:
>>> https://www.sparklan.com/product/wnfq-291bei/
>>>
>>> (I haven't tried it and don't endorse it, just giving as an example)
>>
>> Hello Jeff,
>>
>> Thanks for the link. That too is dual band though. I'm interested in
>> using ath12k radios for wifi testing purposes, so I'd really like tri-band
>> MLO to have some feature parity with the MTK 7996 radio board.
>>
>> Is ath12k able to combine discrete wifi NICs into tri-band MLO stations?
>
> Yes, ath12k supports tri-band MLO STA. This has been validated for QCN chipsets.
> Not sure if this has been tested for WCN chipsets.
Can this work with some combination of Compex radios in an x86 chassis,
or does it require some integrated AP style platform? If x86 is supported,
please suggest some radio model(s) you think will work.
>> Or is ath12k entirely DBDC at this point with no tri-band MLO capability?
>>
>> In addition, back in ath10k days, I was able to get the radio to do up to
>> 64 STA vdevs once I put the firmware on a diet. From a quick look at the ath12k
>> driver, it seems the limit for STA vdevs is exactly 1. Is there any somewhat-documented
>> way to get ath12k to support more STA vdevs?
>
> Supporting more number of STA vdevs instead of the current 1 STA will require
> firmware changes (and of course more validations).
Any idea if QCA is offering ath12k FW source under NDA and/or for some price?
We could likely make the changes and validate, but we need the FW source and
a toolchain to compile it.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2025-11-12 15:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 15:27 ath12k pcie radios with MLO support? Ben Greear
2025-11-11 16:01 ` pgupta
2025-11-12 1:29 ` Jeff Johnson
2025-11-12 1:40 ` Ben Greear
2025-11-12 5:15 ` Vasanthakumar Thiagarajan
2025-11-12 14:57 ` Jeff Johnson
2025-11-13 2:02 ` Baochen Qiang
2025-11-12 15:36 ` Ben Greear [this message]
2025-11-12 16:25 ` Vasanthakumar Thiagarajan
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=3f43654b-3fca-4020-8393-d028991edba1@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath12k@lists.infradead.org \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=vasanthakumar.thiagarajan@oss.qualcomm.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