wgong@xxxxxxxxxxxxxx writes: > On 2019-12-02 18:08, Kalle Valo wrote: >> Wen Gong <wgong@xxxxxxxxxxxxxx> 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 <wgong@xxxxxxxxxxxxxx> >>> Signed-off-by: Kalle Valo <kvalo@xxxxxxxxxxxxxx> >> >> 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. > https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/log/drivers/net/wireless/ath?h=ath-next > 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: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=ath-next&id=2dc016599cfa9672a147528ca26d70c3654a5423 -- https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
