From: Robert Marko <robimarko@gmail.com>
To: kvalo@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, robh@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
jjohnson@kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
ath11k@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Robert Marko <robimarko@gmail.com>
Subject: [PATCH 2/2] wifi: ath11k: support DT ieee80211-freq-limit property to limit channels
Date: Fri, 12 Apr 2024 18:24:09 +0200 [thread overview]
Message-ID: <20240412162510.29483-2-robimarko@gmail.com> (raw)
In-Reply-To: <20240412162510.29483-1-robimarko@gmail.com>
The common DT property can be used to limit the available channels
but ath11k has to manually call wiphy_read_of_freq_limits().
Signed-off-by: Robert Marko <robimarko@gmail.com>
---
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 c32be587000d..59bde128d351 100644
--- a/drivers/net/wireless/ath/ath11k/mac.c
+++ b/drivers/net/wireless/ath/ath11k/mac.c
@@ -10124,6 +10124,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.44.0
next prev parent reply other threads:[~2024-04-12 16:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 16:24 [PATCH 1/2] dt-bindings: net: wireless: ath11k: add ieee80211-freq-limit property Robert Marko
2024-04-12 16:24 ` Robert Marko [this message]
2024-04-12 19:52 ` [PATCH 2/2] wifi: ath11k: support DT ieee80211-freq-limit property to limit channels Christian Lamparter
2024-04-12 20:21 ` Robert Marko
2024-04-12 20:53 ` Jeff Johnson
2024-04-15 16:06 ` Kalle Valo
2024-04-15 16:08 ` Robert Marko
2024-04-16 13:21 ` [PATCH 1/2] dt-bindings: net: wireless: ath11k: add ieee80211-freq-limit property Rob Herring
2024-04-16 13:22 ` Robert Marko
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=20240412162510.29483-2-robimarko@gmail.com \
--to=robimarko@gmail.com \
--cc=ath11k@lists.infradead.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jjohnson@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@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 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.