On 5/3/2024 1:56 PM, Johannes Berg wrote:
On Mon, 2024-04-29 at 09:57 +0530, Harshitha Prem wrote:
Currently, to allow pre-CAC it requires both driver's regulatory domain
in wiphy and cfg80211 local regulatory domain to be same, along with the
region to be in ETSI.
Any idea why that is?
But, for self-managed driver, some countries have mismatch between these
two regulatory domains and it would not allow for a pre-CAC. For example,
in ath12k driver (self-managed), country Sri Lanka (LK) is classified as
FCC domain as per cfg80211 local regulatory database but as per ath12k
driver it falls under ETSI domain then because of this mismatch, the
driver might not be able to do a pre-CAC.
Hence, add changes to allow pre-CAC based on wiphy's regulatory setting
if it is a self-managed wiphy.
I don't see how that's really all that much more helpful than simply
removing the restriction? But then why is the restriction there?
johannes
Hi Johannes,
Seems like, there can be a possibility to have two wiphy devices with
two different regulatory domains to be present on a single system and
for cfg80211 to respect it. In this case, a core central regulatory
domain will consist of the intersection between the two wiphy's
regulatory domains. Because of this mostly, in case of DFS, in cfg80211
apis like reg_get_dfs_region() , there is a check to ensure like if both
the core central regulatory and device's regulatory are same.
Drivers which are not self managed can have this restriction, just to
ensure to allow precac only if both matches or May be should we relax
this restriction? but I am quite not sure on the impact. Will try to
analyze on this.
Thanks,
Harshitha.
