From: Kalle Valo <kvalo@codeaurora.org>
To: Sriram R <srirrama@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH] ath11k: Fix vdev start failure when operating in CN, KR regdomain
Date: Thu, 6 Jun 2019 16:38:25 +0000 (UTC) [thread overview]
Message-ID: <20190606163825.E0DD560E75@smtp.codeaurora.org> (raw)
In-Reply-To: <1559561865-27928-1-git-send-email-srirrama@codeaurora.org>
Sriram R <srirrama@codeaurora.org> wrote:
> Currently, firmware expects the correct regdomain to be set in
> vdev start command. As firmware supports regulatory offload, it can track
> the current regdomain. This info is received from firmware via
> REG_CHAN_LIST_CC event during bringup or after setting country code.
> Currently the dfs_region received is mapped to nl80211_dfs_regions
> and stored in default_regd or new_regd and is used for vdev start.
> But since nl80211_dfs_regions doesn't have a value enumerated for CN
> KR, the firmware rejects VDEV start with an 'invalid regdomain' error.
> Hence, send the appropriate regdomain received from firmware during
> REG_CHAN_LIST_CC event in vdev start to avoid vdev start failure.
>
> Signed-off-by: Sriram R <srirrama@codeaurora.org>
Patch applied to ath.git, thanks.
b0d742f32bc3 ath11k: Fix vdev start failure when operating in CN, KR regdomain
--
https://patchwork.kernel.org/patch/10972787/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2019-06-06 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 11:37 [PATCH] ath11k: Fix vdev start failure when operating in CN, KR regdomain Sriram R
2019-06-06 16:38 ` Kalle Valo [this message]
2019-06-06 16:48 ` Kalle Valo
2019-06-13 0:30 ` Sriram R
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=20190606163825.E0DD560E75@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=srirrama@codeaurora.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