From: Sven Eckelmann <sven@narfation.org>
To: ath11k@lists.infradead.org, Wen Gong <quic_wgong@quicinc.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath11k: add regdb.bin download for regdb offload
Date: Thu, 02 Dec 2021 19:36:35 +0100 [thread overview]
Message-ID: <2715590.fzSe1J7v7S@sven-l14> (raw)
In-Reply-To: <20211202083616.15406-1-quic_wgong@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
On Thursday, 2 December 2021 09:36:16 CET Wen Gong wrote:
> The regdomain is self-managed type for ath11k, the regdomain info is
> reported from firmware, it is not from wireless regdb. Firmware fetch
> the regdomain info from board data file before. Currently most of the
> regdomain info has moved to another file regdb.bin from board data
> file for some chips such as QCA6390 and WCN6855, so the regdomain info
> left in board data file is not enough to support the feature which need
> more reg rules such as 6 GHz LPI, SP and VLP.
But for the latter, you are also missing the patch to support the
WMI_REG_CHAN_LIST_CC_EXT_EVENTID (with the 6GHz specific fields in the struct
wmi_reg_chan_list_cc_ext_event)? Otherwise it should not be possible to
get the 6GHz reg rules (which you showed in your commit message).
struct wmi_reg_chan_list_cc_event (for WMI_REG_CHAN_LIST_CC_EVENTID) supports
only 2.4GHz and 5GHz.
Kind regards,
Sven
[1] https://source.codeaurora.org/quic/qsdk/oss/system/feeds/wlan-open/tree/mac80211/patches/302-ath11k-Add-support-to-parse-new-wmi-event-for-6G-reg.patch?h=NHSS.QSDK.11.4.0.5
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-12-02 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 8:36 [PATCH] ath11k: add regdb.bin download for regdb offload Wen Gong
2021-12-02 18:36 ` Sven Eckelmann [this message]
2021-12-03 4:50 ` Wen Gong
2021-12-14 18:08 ` Kalle Valo
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=2715590.fzSe1J7v7S@sven-l14 \
--to=sven@narfation.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_wgong@quicinc.com \
/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