archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <>
Subject: Re: [PATCH] ath: add support for special 0x0 regulatory domain
Date: Mon, 2 Dec 2019 10:24:14 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> ('s message of "Mon, 02 Dec 2019 18:14:51 +0800") writes:

> On 2019-12-02 18:08, Kalle Valo wrote:
>> Wen Gong <> wrote:
>>> Some sdio chips of rome QCA6174's regulatory domain code of EEPROM is
>>> empty, then ath_is_world_regd will return false for this case, and
>>> it will lead function __ath_reg_dyn_country not work, thus the
>>> regdomain
>>> will not update for NL80211_REGDOM_SET_BY_COUNTRY_IE type, it result
>>> ath10k set the same regdomain/reg_5ghz_ctl/reg_2ghz_ctl to firmware,
>>> then the tx power will not changed with different regdomain's AP. The
>>> regulatory domain code of EEPROM of some QCA6174 PCIE chip is 0x6c, it
>>> means world wide regdomain, for this chip, it does not have the issue.
>>> For empty reulatory domain code chip, set it to world regulatory
>>> domain
>>> in functio ath_regd_sanitize, then it will fix the issue.
>>> Tested with QCA6174 SDIO with firmware
>>> WLAN.RMH.4.4.1-00029.
>>> Signed-off-by: Wen Gong <>
>>> Signed-off-by: Kalle Valo <>
>> Patch applied to ath-next branch of ath.git, thanks.
>> 2dc016599cfa ath: add support for special 0x0 regulatory domain
> But I did not see it in ath-next now.
> is it has some delay?

Yes, it takes some time for me to apply other patches, merge branches,
servers sync etc. If you don't see the commit in the repository in 2
hours from me sending the "applied" mail, then do let me know as
something might be wrong. But before that just wait patiently :)

But now the commit is there:


ath10k mailing list

  parent reply	other threads:[~2019-12-02 10:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2019-12-02 10:08 ` [PATCH] ath: add support for special 0x0 regulatory domain Kalle Valo
     [not found] ` <>
2019-12-02 10:14   ` wgong
     [not found]   ` <>
2019-12-02 10:24     ` Kalle Valo [this message]
     [not found] <>
2020-12-22  3:42 ` Wen Gong
2020-12-22 18:30   ` Brian Norris
2020-12-23 11:01     ` Kalle Valo
2020-12-23 18:18       ` Brian Norris
2021-01-04 12:10       ` Alvin Šipraga
2019-11-29  7:34 Wen Gong

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).