From: Rob Herring <robh@kernel.org>
To: Christian Lamparter <chunkeey@gmail.com>
Cc: devicetree@vger.kernel.org, linux-wireless@vger.kernel.org,
ath11k@lists.infradead.org, kvalo@kernel.org,
conor+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org
Subject: Re: [PATCH v1 1/2] dt-bindings: net: ath11k: add ieee80211-freq-limit property
Date: Fri, 9 Jun 2023 10:51:04 -0600 [thread overview]
Message-ID: <20230609165104.GA1257474-robh@kernel.org> (raw)
In-Reply-To: <a3075482150d342f71ec235badacec32cdd6c553.1686300243.git.chunkeey@gmail.com>
On Fri, Jun 09, 2023 at 10:44:54AM +0200, 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.
>
> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
> ---
> Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml b/Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml
> index 7d5f982a3d09..91bf69c2df01 100644
> --- a/Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml
> +++ b/Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml
> @@ -58,6 +58,8 @@ properties:
> minItems: 1
> maxItems: 2
>
> + ieee80211-freq-limit: true
> +
You need a ref to ieee80211.yaml as well.
> wifi-firmware:
> type: object
> description: |
> --
> 2.40.1
>
next prev parent reply other threads:[~2023-06-09 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 8:44 [PATCH v1 1/2] dt-bindings: net: ath11k: add ieee80211-freq-limit property Christian Lamparter
2023-06-09 8:44 ` [PATCH v1 2/2] wifi: ath11k: add support DT ieee80211-freq-limit Christian Lamparter
2023-06-09 15:49 ` [PATCH v1 1/2] dt-bindings: net: ath11k: add ieee80211-freq-limit property Conor Dooley
2023-06-09 16:51 ` Rob Herring [this message]
2023-06-09 17:11 ` Christian Lamparter
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=20230609165104.GA1257474-robh@kernel.org \
--to=robh@kernel.org \
--cc=ath11k@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 \
/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).