From: Petros Christopoulos <petros.christopoulos@gmail.com>
To: Baochen Qiang <baochen.qiang@oss.qualcomm.com>,
ath12k@lists.infradead.org
Subject: Re: Enabling 6 GHz band in WCN785x
Date: Wed, 13 Aug 2025 08:50:20 +0200 [thread overview]
Message-ID: <b0169ce8-3a9c-482b-a99c-d8bde8be2980@gmail.com> (raw)
In-Reply-To: <3ae5fcec-bfa4-4d41-8ee6-2c26ce0e4f51@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 6753 bytes --]
Dear Baochen,
great, thank you very much for the prompt and clear reply.
Indeed with the new kernel (6.16.0) when I connect to an AP in DE, the
Wifi module switches to DE and keeps the DE region even after
disconnection and reboot.
This was not possible with the previous kernel 6.15.9 (I had already
tested it with the same AP as now, but no success).
Thus, my basic problem is solved, and I also now know how to enable
manual switching.
Thanks a lot for the advice and above all for the excellent developer
work behind implementation!
Best wishes,
Petros
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(5945 - 6425 @ 320), (N/A, 23), (N/A), NO-OUTDOOR
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#0 (self-managed)
country DE: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5490 - 5590 @ 80), (N/A, 30), (0 ms), DFS, AUTO-BW
(5590 - 5650 @ 40), (N/A, 30), (600000 ms), DFS, AUTO-BW
(5650 - 5710 @ 40), (N/A, 30), (0 ms), DFS, AUTO-BW
(5735 - 5855 @ 80), (N/A, 14), (N/A), AUTO-BW
(5855 - 5875 @ 20), (N/A, 14), (N/A), AUTO-BW
(5945 - 6425 @ 320), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
On 13.08.2025 05:13, Baochen Qiang wrote:
>
> On 8/13/2025 6:22 AM, Petros Christopoulos wrote:
>> Dear Baochen,
>>
>> I tried the kernel 6.16.0 today (kernel-6.16.0-200.fc42.x86_64.rpm; it is Fedora kernel
>> test week now) which contains the commit dcfebfd4c8dc0bec9b6649104cecc09f5978c4cb
>> (=revision v6.16-rc1~132^2~157^2~16^2~62)
>>
>> but the behavior regarding the Wifi module WCN785x has not changed:
>>
>> despite sudo iw reg set DE,
>> phy#0 remains self managed (see below at the end)
>>
>> However, the option CONFIG_ATH_REG_DYNAMIC_USER_REG_HINTS is not enabled in the Fedora
>> kernel, and I have asked the maintainers if this could be enabled (everything is of course
>> simpler if I do not have to recompile every kernel myself, https://bugzilla.redhat.com/
>> show_bug.cgi?id=2387486)
>>
>> I noticed this option is relevant inside the ath12k code, e.g.
>>
>> $ grep -r CONFIG_ATH_REG_DYNAMIC_USER_REG_HINTS drivers/net/wireless/ath/ath12k/
>> drivers/net/wireless/ath/ath12k/reg.c: if (!
>> IS_ENABLED(CONFIG_ATH_REG_DYNAMIC_USER_REG_HINTS)) {
>>
>> Could you please let me know:
>>
>> 1. whether having this option enebled in the kernel is absolutely necessary for the
>> ability to change the region or there are also alternatives?
> The option is only necessary if you want to manually set the country code. Normally the
> driver/firmware should be able to detect automatically the country from AP's frames using
> 11D feature.
>
> 11D feature takes some time to detect country info, so please wait, say at least 1 minute,
> before you make conclusion. If still fail, please help collect verbose ath12k log with
>
> modprobe ath12k debug_mask=0xffffffff
>
>> 2. whether if this option is enabled with kernel 6.16.0 (with the commit above), I should
>> be able to change the region of the WCN785x module with a simple sudo iw reg set DE, or
>> whether still another special method will be necessary?
> Enabling CONFIG_ATH_REG_DYNAMIC_USER_REG_HINTS will let you be able to set country code
> using iw. There is no alternative for this purpose.
>
>> Thank you very much and kind regards
>>
>> Petros
>>
>>
>> global
>> country DE: DFS-ETSI
>> (2400 - 2483 @ 40), (N/A, 20), (N/A)
>> (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
>> (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
>> (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
>> (5725 - 5875 @ 80), (N/A, 13), (N/A)
>> (5945 - 6425 @ 320), (N/A, 23), (N/A), NO-OUTDOOR
>> (57000 - 66000 @ 2160), (N/A, 40), (N/A)
>>
>> phy#0 (self-managed)
>> country 00: DFS-UNSET
>> (2402 - 2472 @ 40), (N/A, 20), (N/A)
>> (2457 - 2482 @ 20), (N/A, 20), (N/A), PASSIVE-SCAN
>> (5170 - 5330 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
>> (5490 - 5730 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
>> (5735 - 5895 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
>>
>>
>>
>>
>>
>>
>>
>> On 12.08.2025 05:21, Baochen Qiang wrote:
>>> On 8/10/2025 9:56 PM, Petros Christopoulos wrote:
>>>> Dear all, I have a Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2
>>>> [FastConnect 7800] [17cb:1107] (rev 01) Wifi controller
>>>> with Fedora 42 KDE, latest kernel 6.15.9-201.fc42.x86_64 and recent firmware 0x1108811c
>>>> fw_build_timestamp 2025-05-17 00:21 fw_build_id
>>>> QC_IMAGE_VERSION_STRING=WLAN.HMT.1.1.c5-00284.1-QCAHMTSWPL_V1.0_V2.0_SI
>>>> LICONZ-3
>>>>
>>>> The 6 GHz band is disabled, I suspect that the problem is the 00 region setting in phy#1,
>>>> however as this is "self-managed" I have not managed to change this (iw reg set or an /
>>>> etc/modprobe.d/ath12k.conf file with "options ath12k country=DE" have no effects).
>>> Try with CONFIG_ATH_REG_DYNAMIC_USER_REG_HINTS enabled.
>>>
>>>> $ iw reg get
>>>> global
>>>> country DE: DFS-ETSI
>>>> (2400 - 2483 @ 40), (N/A, 20), (N/A)
>>>> (5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
>>>> (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
>>>> (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
>>>> (5725 - 5875 @ 80), (N/A, 13), (N/A)
>>>> (5945 - 6425 @ 320), (N/A, 23), (N/A), NO-OUTDOOR
>>>> (57000 - 66000 @ 2160), (N/A, 40), (N/A)
>>>>
>>>> phy#1 (self-managed)
>>>> country 00: DFS-UNSET
>>>> (2402 - 2472 @ 40), (N/A, 20), (N/A)
>>>> (2457 - 2482 @ 20), (N/A, 20), (N/A), PASSIVE-SCAN
>>>> (5170 - 5330 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
>>>> (5490 - 5730 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
>>>> (5735 - 5895 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
>>>>
>>>> I have searched extensively the web, found some relevant articles (e.g. https://
>>>> patchwork.kernel.org/project/linux-wireless/patch/20250401020840.357-5-
>>>> quic_kangyang@quicinc.com/, which should be integrated into 6.15.9 if I understand
>>>> correctly), but still no solution.
>>> Do you mean with the whole 11D support series merged the issue is still seen?
>>>
>>>> I would be grateful for some help.
>>>>
>>>> Thank you very much.
>>>>
>>>>
>>>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4760 bytes --]
next prev parent reply other threads:[~2025-08-13 7:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-10 13:56 Enabling 6 GHz band in WCN785x Petros Christopoulos
2025-08-11 14:42 ` Jeff Johnson
2025-08-12 3:21 ` Baochen Qiang
2025-08-12 22:22 ` Petros Christopoulos
2025-08-13 3:13 ` Baochen Qiang
2025-08-13 6:50 ` Petros Christopoulos [this message]
2025-08-13 8:57 ` Baochen Qiang
2025-08-13 9:43 ` Petros Christopoulos
2025-08-14 2:52 ` Baochen Qiang
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=b0169ce8-3a9c-482b-a99c-d8bde8be2980@gmail.com \
--to=petros.christopoulos@gmail.com \
--cc=ath12k@lists.infradead.org \
--cc=baochen.qiang@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