From: Luca Weiss <luca@z3ntu.xyz>
To: Loic Poulain <loic.poulain@linaro.org>,
Stephan Gerhold <stephan@gerhold.net>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Kalle Valo <kvalo@kernel.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Stephan Gerhold <stephan.gerhold@kernkonzept.com>,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
wcn36xx@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: remoteproc: qcom: wcnss: Add WCN3680B compatible
Date: Sat, 25 Nov 2023 13:25:22 +0100 [thread overview]
Message-ID: <1868698.tdWV9SEqCh@z3ntu.xyz> (raw)
In-Reply-To: <ZS1MTAHq6GLW6RAK@gerhold.net>
On Montag, 16. Oktober 2023 16:44:28 CET Stephan Gerhold wrote:
> On Mon, Oct 16, 2023 at 03:16:14PM +0200, Loic Poulain wrote:
> > On Mon, 16 Oct 2023 at 07:35, Krzysztof Kozlowski
> >
> > <krzysztof.kozlowski@linaro.org> wrote:
> > > On 15/10/2023 22:03, Luca Weiss wrote:
> > > > Add a compatible for the iris subnode in the WCNSS PIL.
> > > >
> > > > Signed-off-by: Luca Weiss <luca@z3ntu.xyz>
> > > > ---
> > > >
> > > > Documentation/devicetree/bindings/remoteproc/qcom,wcnss-pil.yaml | 1
> > > > +
> > > > 1 file changed, 1 insertion(+)
> > > >
> > > > diff --git
> > > > a/Documentation/devicetree/bindings/remoteproc/qcom,wcnss-pil.yaml
> > > > b/Documentation/devicetree/bindings/remoteproc/qcom,wcnss-pil.yaml
> > > > index 45eb42bd3c2c..0e5e0b7a0610 100644
> > > > --- a/Documentation/devicetree/bindings/remoteproc/qcom,wcnss-pil.yaml
> > > > +++ b/Documentation/devicetree/bindings/remoteproc/qcom,wcnss-pil.yaml
> > > >
> > > > @@ -111,6 +111,7 @@ properties:
> > > > - qcom,wcn3660
> > > > - qcom,wcn3660b
> > > > - qcom,wcn3680
> > > >
> > > > + - qcom,wcn3680b
> > >
> > > Looks like this should be made as compatible with qcom,wcn3680 (so with
> > > fallback).
> >
> > Yes, agree, let's do a regular fallback as there is nothing 'b'
> > specific in the driver:
> > `compatible = "qcom,wcn3680b", "qcom,wcn3680";`
> >
> > And yes, we should also have done that for qcom,wcn3660b...
>
> I don't think this would have worked properly for qcom,wcn3660b:
>
> - It's not compatible with "qcom,wcn3660", because they have different
> regulator voltage requirements. wcn3660(a?) needs vddpa with
> 2.9-3.0V, but wcn3660b needs 3.3V. That's why wcn3660b uses the
> wcn3680_data in qcom_wcnss.iris.c. Otherwise if you would run an
> older kernel that knows "qcom,wcn3660" but not "qcom,wcn3660b" it
> would apply the wrong voltage.
>
> - It's not compatible with "qcom,wcn3680" either because that is used
> as indication if 802.11ac is supported (wcn3660b doesn't).
>
> The main question here is: What does the current "qcom,wcn3680"
> compatible actually represent? It's defined with vddpa = 3.3V in the
> driver, which would suggest that:
>
> 1. It's actually meant to represent WCN3680B, which needs 3.3V vddpa
> like WCN3660B, or
>
> 2. WCN3680(A?) has different requirements than WCN3660(A?) and also
> needs 3.3V vddpa. But then what is the difference between
> WCN3680(A?) and WCN3680B? Is there even a variant without ...B?
>
> There is public documentation for WCN3660B and WCN3680B but the non-B
> variants are shrouded in mystery.
Hi Stephan (and everyone),
Do you have a suggestion how to move this patchset forward? Is the fallback
compatible that was suggested okay for the wcn3680b situation?
compatible = "qcom,wcn3680b", "qcom,wcn3680";
If so, I'll make v2 with that implemented.
Regards
Luca
>
> Thanks,
> Stephan
next prev parent reply other threads:[~2023-11-25 12:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 20:03 [PATCH 0/4] Add WCN3680B WiFi/Bluetooth and enable it on Fairphone 3 Luca Weiss
2023-10-15 20:03 ` [PATCH 1/4] dt-bindings: remoteproc: qcom: wcnss: Add WCN3680B compatible Luca Weiss
2023-10-16 5:35 ` Krzysztof Kozlowski
2023-10-16 13:16 ` Loic Poulain
2023-10-16 14:44 ` Stephan Gerhold
2023-11-25 12:25 ` Luca Weiss [this message]
2023-11-27 20:07 ` Stephan Gerhold
2023-11-27 20:27 ` Luca Weiss
2023-10-15 20:03 ` [PATCH 2/4] remoteproc: qcom_wcnss: " Luca Weiss
2023-10-16 5:35 ` Krzysztof Kozlowski
2023-10-17 16:28 ` Konrad Dybcio
2023-10-15 20:03 ` [PATCH 3/4] wifi: wcn36xx: Add check for WCN3680B Luca Weiss
2023-10-16 5:36 ` Krzysztof Kozlowski
2023-10-15 20:03 ` [PATCH 4/4] arm64: dts: qcom: sdm632-fairphone-fp3: Enable WiFi/Bluetooth Luca Weiss
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=1868698.tdWV9SEqCh@z3ntu.xyz \
--to=luca@z3ntu.xyz \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kvalo@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=mathieu.poirier@linaro.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=stephan.gerhold@kernkonzept.com \
--cc=stephan@gerhold.net \
--cc=wcn36xx@lists.infradead.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).