linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Christian Lamparter <chunkeey@gmail.com>,
	devicetree@vger.kernel.org, linux-wireless@vger.kernel.org,
	ath10k@lists.infradead.org
Cc: kvalo@kernel.org, conor+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org
Subject: Re: [PATCH v2] dt-bindings: net: wireless: ath10k: add ieee80211-freq-limit property
Date: Mon, 12 Jun 2023 10:42:00 +0200	[thread overview]
Message-ID: <bd95ab0c-402b-0914-0d3f-5309a63d8eea@linaro.org> (raw)
In-Reply-To: <c33c928b7c6c9bb4e7abe84eb8df9f440add275b.1686486464.git.chunkeey@gmail.com>

On 11/06/2023 14:37, Christian Lamparter wrote:
> This is an existing optional property that ieee80211.yaml/cfg80211
> provides. It's useful to further restrict supported frequencies
> for a specified device through device-tree.
> 
> For testing the addition, I added the ieee80211-freq-limit
> property with values from an OpenMesh A62 device. This is
> because the OpenMesh A62 has "special filters in front of
> the RX+TX paths to the 5GHz PHYs. These filtered channel
> can in theory still be used by the hardware but the signal
> strength is reduced so much that it makes no sense."
> 
> The driver supported this since ~2018 by
> commit 34d5629d2ca8 ("ath10k: limit available channels via DT ieee80211-freq-limit")
> 
> Link: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=e3b8ae2b09e137ce2eae33551923daf302293a0c
> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>


Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Best regards,
Krzysztof


  reply	other threads:[~2023-06-12  8:42 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 [this message]
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   ` [PATCH v2 2/2] wifi: ath11k: add support DT ieee80211-freq-limit Christian Lamparter
2023-06-12  8:41   ` [PATCH v2 1/2] dt-bindings: net: wireless: ath11k: add ieee80211-freq-limit property 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=bd95ab0c-402b-0914-0d3f-5309a63d8eea@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=ath10k@lists.infradead.org \
    --cc=chunkeey@gmail.com \
    --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).