[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d1c6093d-5f3b-176e-56d6-a46af4c13c5a@linaro.org>
Date: Tue, 20 Sep 2022 11:55:02 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Sireesh Kodali <sireeshkodali1@...il.com>,
devicetree@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-remoteproc@...r.kernel.org,
~postmarketos/upstreaming@...ts.sr.ht
Cc: andersson@...nel.org, Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Konrad Dybcio <konrad.dybcio@...ainline.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 3/4] dt-bindings: remoteproc: qcom: wcnss: Add
qcom,pronto compatible
On 20/09/2022 05:03, Sireesh Kodali wrote:
> This is not a fallback compatible, it must be present in addition to
> "qcom,pronto-v*". It is also not documented in qcom,wcnss-pil.txt. This
> is the reason for documenting it in a separate commit.
>
> This compatible is used in the wcn36xx driver to determine which
> register must be accessed. However it isn't immediately clear why the
> wcn36xx driver relies on this extra compatible string rather than just
> looking for "qcom,pronto-v*".
>
> Signed-off-by: Sireesh Kodali <sireeshkodali1@...il.com>
It's a v3. What are the changes?
Best regards,
Krzysztof
Powered by blists - more mailing lists