From: Christian Lamparter <chunkeey@gmail.com>
To: devicetree@vger.kernel.org, linux-wireless@vger.kernel.org,
ath11k@lists.infradead.org
Cc: kvalo@kernel.org, conor+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org
Subject: [PATCH v2 2/2] wifi: ath11k: add support DT ieee80211-freq-limit
Date: Sun, 11 Jun 2023 14:37:32 +0200 [thread overview]
Message-ID: <ed266944c721de8dbf0fe35f387a3a71b2c84037.1686486468.git.chunkeey@gmail.com> (raw)
In-Reply-To: <fc606d2550d047a53b4289235dd3c0fe23d5daac.1686486468.git.chunkeey@gmail.com>
The common DT property can be used to limit the available
channels/frequencies. But ath11k has to manually call
wiphy_read_of_freq_limits().
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
---
compile-tested only.
---
drivers/net/wireless/ath/ath11k/mac.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/wireless/ath/ath11k/mac.c b/drivers/net/wireless/ath/ath11k/mac.c
index c947d1c8d8c1..7e43f2770f27 100644
--- a/drivers/net/wireless/ath/ath11k/mac.c
+++ b/drivers/net/wireless/ath/ath11k/mac.c
@@ -9414,6 +9414,7 @@ static int __ath11k_mac_register(struct ath11k *ar)
if (ret)
goto err;
+ wiphy_read_of_freq_limits(ar->hw->wiphy);
ath11k_mac_setup_ht_vht_cap(ar, cap, &ht_cap);
ath11k_mac_setup_he_cap(ar, cap);
--
2.40.1
next prev parent reply other threads:[~2023-06-11 12:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 12:37 [PATCH v1] dt-bindings: net: wireless: bcm4329-fmac: add ieee80211-freq-limit property Christian Lamparter
2023-06-11 12:37 ` [PATCH v2] dt-bindings: net: wireless: ath10k: " Christian Lamparter
2023-06-12 8:42 ` Krzysztof Kozlowski
2023-06-16 16:17 ` Kalle Valo
2023-06-11 12:37 ` [PATCH v2 1/2] dt-bindings: net: wireless: ath11k: " Christian Lamparter
2023-06-11 12:37 ` Christian Lamparter [this message]
2023-06-12 8:41 ` Krzysztof Kozlowski
2024-04-18 15:19 ` Kalle Valo
2023-06-12 8:42 ` [PATCH v1] dt-bindings: net: wireless: bcm4329-fmac: " Krzysztof Kozlowski
2023-06-12 18:23 ` Rafał Miłecki
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=ed266944c721de8dbf0fe35f387a3a71b2c84037.1686486468.git.chunkeey@gmail.com \
--to=chunkeey@gmail.com \
--cc=ath11k@lists.infradead.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).