From: Vitor Soares <ivitro@gmail.com>
To: Jeff Johnson <jjohnson@kernel.org>, Wen Gong <quic_wgong@quicinc.com>
Cc: ath12k@lists.infradead.org, linux-wireless@vger.kernel.org,
Kalle Valo <kvalo@kernel.org>,
vdosreis@qti.qualcomm.com, lucia@qti.qualcomm.com,
dbenitez@qti.qualcomm.com, jeff.johnson@oss.qualcomm.com,
bqiang@qti.qualcomm.com, wgan@qti.qualcomm.com
Subject: Re: ath12k: recommended regulatory country source for embedded AP products?
Date: Mon, 17 Aug 2026 16:04:35 +0100 [thread overview]
Message-ID: <c7609911037798c2026636ddd13208cdf000cc55.camel@gmail.com> (raw)
In-Reply-To: <3ac168e7dfe22133daf09adc3f6587098ec85619.camel@gmail.com>
Hello,
Adding a few Qualcomm contacts in Cc who may be able to help here, or point me
to the right people.
Thanks,
Vitor Soares
On Wed, 2026-07-29 at 10:29 +0100, Vitor Soares wrote:
> Hello,
>
> I'm integrationg the Silex SX-PCEBE module (Qualcomm WCN7850, ath12k) on the
> ARM-based Toradex Aquila SoM family, using a recent mainline kernel (7.2-rc).
>
> Hardware/firmware: wcn7850 hw2.0 (PCI),
> WLAN.HMT.1.1.c7-00108-QCAHMTSWPL_V1.0_V2.0_SILICONZ_UPSTREAM-3
> (fw_version 0x1103006c).
>
> I'm trying to understand the intended way to set the regulatory country for
> ath12k on embedded products where the country is configured by the integrator
> of
> our SoM or at deployment time by the end user.
>
> My current understanding is that ath12k registers the wiphy as self-managed,
> but
> userspace regulatory hints, e.g. "iw reg", are ignored in
> ath12k_reg_notifier()
> unless CONFIG_ATH_REG_DYNAMIC_USER_REG_HINTS=y, which in turn depends on
> CONFIG_CFG80211_CERTIFICATION_ONUS.
>
> The SMBIOS coounty-code path, looks intended for fixed regional SKUs, However,
> it is not available on our ARM platform.
>
> So, I have 2 related questions:
>
> 1 - Is the expected ath12k model for this type of product to enable
> ATH_REG_DYNAMIC_USER_REG_HINTS and use userspace regulatory hints before
> starting hostapd, with the regulatory responsibility on the
> product/integrator?
>
>
> Or is there another mechanism you would recomment for this use case?
>
> 2 - Since ath12k is a self-managed regulatory device and the firmware owns and
> enforces the regulatory database, is the CFG80211_CERTIFICATION_ONUS gate
> intended to apply to this case as well?
>
> In other words, should a userspace-selected country for a self-managed ath12k
> device be treated the same as dynamic user regulatory hints for non-self-
> managed
> devices, or is this dependency inherited from the common ath regulatory model?
>
> Without a country, the ath12k falls back to world "00", where 5 GHz AP
> operation
> is blocked by NO_IR.
>
> Thanks,
> Vitor Soares
>
next prev parent reply other threads:[~2026-08-17 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 9:29 ath12k: recommended regulatory country source for embedded AP products? Vitor Soares
2026-08-17 15:04 ` Vitor Soares [this message]
2026-08-17 15:17 ` Vitor Soares
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=c7609911037798c2026636ddd13208cdf000cc55.camel@gmail.com \
--to=ivitro@gmail.com \
--cc=ath12k@lists.infradead.org \
--cc=bqiang@qti.qualcomm.com \
--cc=dbenitez@qti.qualcomm.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lucia@qti.qualcomm.com \
--cc=quic_wgong@quicinc.com \
--cc=vdosreis@qti.qualcomm.com \
--cc=wgan@qti.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