From: Johan Hovold <johan@kernel.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: Johan Hovold <johan+linaro@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: wireless: add ath11k pcie bindings
Date: Mon, 20 Mar 2023 13:42:11 +0100 [thread overview]
Message-ID: <ZBhUo1C08U5mp9zP@hovoldconsulting.com> (raw)
In-Reply-To: <87ttyfhatn.fsf@kernel.org>
On Mon, Mar 20, 2023 at 02:22:12PM +0200, Kalle Valo wrote:
> Johan Hovold <johan+linaro@kernel.org> writes:
>
> > Add devicetree bindings for Qualcomm ath11k PCIe devices such as WCN6856
> > for which the calibration data variant may need to be described.
> >
> > Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
> > ---
> > .../bindings/net/wireless/pci17cb,1103.yaml | 56 +++++++++++++++++++
> > 1 file changed, 56 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/net/wireless/pci17cb,1103.yaml
>
> I'm confused (as usual), how does this differ from
> bindings/net/wireless/qcom,ath11k.yaml? Why we need two .yaml files?
Almost none of bindings/net/wireless/qcom,ath11k.yaml applies to WCN6856
when using PCIe (e.g. as most properties are then discoverable).
We could try to encode everything in one file, but that would likely
just result in a big mess of a schema with conditionals all over.
Johan
next prev parent reply other threads:[~2023-03-20 12:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 10:46 [PATCH 0/3] arm64: dts: qcom: sc8280xp-x13s: add wifi calibration variant Johan Hovold
2023-03-20 10:46 ` [PATCH 1/3] dt-bindings: wireless: add ath11k pcie bindings Johan Hovold
2023-03-20 12:22 ` Kalle Valo
2023-03-20 12:42 ` Johan Hovold [this message]
2023-03-20 18:41 ` Kalle Valo
2023-03-21 8:22 ` Johan Hovold
2023-03-22 5:59 ` Kalle Valo
2023-03-21 8:14 ` Krzysztof Kozlowski
2023-03-21 8:16 ` Krzysztof Kozlowski
2023-03-21 8:27 ` Johan Hovold
2023-03-21 8:29 ` Krzysztof Kozlowski
2023-03-20 10:46 ` [PATCH 2/3] arm64: dts: qcom: sc8280xp-x13s: add wifi calibration variant Johan Hovold
2023-03-20 10:59 ` Konrad Dybcio
2023-03-20 12:15 ` Steev Klimaszewski
2023-03-20 10:46 ` [PATCH 3/3] arm64: dts: qcom: sc8280xp-crd: " Johan Hovold
2023-03-20 10:50 ` Konrad Dybcio
2023-03-20 10:55 ` Johan Hovold
2023-03-20 10:59 ` Konrad Dybcio
2023-03-20 11:07 ` Johan Hovold
2023-03-20 12:18 ` Kalle Valo
2023-03-20 12:34 ` Johan Hovold
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=ZBhUo1C08U5mp9zP@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-arm-msm@vger.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+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).