From: Sriram R <srirrama@codeaurora.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH] ath11k: Fix vdev start failure when operating in CN, KR regdomain
Date: Thu, 13 Jun 2019 06:00:52 +0530 [thread overview]
Message-ID: <2236c335e44587db2e928bdf5150a0aa@codeaurora.org> (raw)
In-Reply-To: <878suevevc.fsf@kamboji.qca.qualcomm.com>
On 2019-06-06 22:18, Kalle Valo wrote:
> Kalle Valo <kvalo@codeaurora.org> writes:
>
>> 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
>
> This added a new warning:
>
> drivers/net/wireless/ath/ath11k/wmi.c:4655:34: warning: mixing
> different enum types
> drivers/net/wireless/ath/ath11k/wmi.c:4655:34: unsigned int enum
> dfs_reg versus
> drivers/net/wireless/ath/ath11k/wmi.c:4655:34: unsigned int enum
> ath11k_dfs_region
>
> Please send a followup patch to fix that.
Sure Kalle. These warnings got subsided during my compilation and they
look
valid. I'll send a followup patch.
Regards,
Sriram.R
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2019-06-13 0:30 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
2019-06-06 16:48 ` Kalle Valo
2019-06-13 0:30 ` Sriram R [this message]
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=2236c335e44587db2e928bdf5150a0aa@codeaurora.org \
--to=srirrama@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=kvalo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.