From: Alexander Wilhelm <alexander.wilhelm@westermo.com>
To: Jeff Johnson <jjohnson@kernel.org>
Cc: ath12k@lists.infradead.org, linux-firmware@kernel.org
Subject: ath12k: inconsistent regdb for QCN9274
Date: Tue, 8 Sep 2026 08:46:36 +0200 [thread overview]
Message-ID: <ap-vTGZiqGaodxKE@FUE-ALEWI-WINX> (raw)
Hello Developers,
I am using QCN9274 chipsets with the `ath12k` driver on my devices. As far as I
can tell, the driver uses the regulatory database from the `board-2.bin` file.
However, some country definitions do not appear to be fully implemented, as the
values differ from those in Linux's standard `wireless-regdb` repository. I even
downloaded the latest `linux-firmware-20260810.tar.xz` and do not see any
related changes there.
For example, when switching to DE, I see the following values:
* Channels 52-64: 23 dBm; I would expect 20.0 dBm
* Channels 100-140: 30.0 dBm; I would expect 26.0 dBm
* Channels 144-173: (disabled); I would expect 13.0 dBm
US also appears to be inconsistent:
* Channels 36-48: 30.0 dBm; I would expect 23.0 dBm
* Channels 169-173: (disabled); I would expect 30.0 dBm
I am aware that `wireless-regdb` is intentionally restrictive in some cases. For
example, there are rules where 26.0 dBm is used instead of 30.0 dBm because it
is implicitly assumed that TPC is not supported. Therefore, some differences may
be expected.
However, the values above still appear to be incorrect. Could someone at
Qualcomm please investigate this and fix the regulatory information if it is
indeed wrong? If the current behavior is intentional, I would appreciate an
explanation of how these limits are derived, as they do not seem to match either
the `wireless-regdb` entries or the applicable regulatory requirements. Thank
you in advance.
Best regards
Alexander Wilhelm
reply other threads:[~2026-09-08 6:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ap-vTGZiqGaodxKE@FUE-ALEWI-WINX \
--to=alexander.wilhelm@westermo.com \
--cc=ath12k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-firmware@kernel.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