From: Sireesh Kodali <sireeshkodali1@gmail.com>
To: devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-remoteproc@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Cc: andersson@kernel.org, Sireesh Kodali <sireeshkodali1@gmail.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH v3 3/4] dt-bindings: remoteproc: qcom: wcnss: Add qcom,pronto compatible
Date: Tue, 20 Sep 2022 08:33:15 +0530 [thread overview]
Message-ID: <20220920030316.1619781-4-sireeshkodali1@gmail.com> (raw)
In-Reply-To: <20220920030316.1619781-1-sireeshkodali1@gmail.com>
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@gmail.com>
---
.../bindings/remoteproc/qcom,wcnss-pil.yaml | 13 +++++++++----
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,wcnss-pil.yaml b/Documentation/devicetree/bindings/remoteproc/qcom,wcnss-pil.yaml
index bb499ae9a4f0..31232c59b22b 100644
--- a/Documentation/devicetree/bindings/remoteproc/qcom,wcnss-pil.yaml
+++ b/Documentation/devicetree/bindings/remoteproc/qcom,wcnss-pil.yaml
@@ -15,10 +15,15 @@ description:
properties:
compatible:
- enum:
- - qcom,riva-pil
- - qcom,pronto-v1-pil
- - qcom,pronto-v2-pil
+ description:
+ Append "qcom,pronto" if the device is actually pronto, and not riva
+ oneOf:
+ - items:
+ - enum:
+ - qcom,pronto-v1-pil
+ - qcom,pronto-v2-pil
+ - const: qcom,pronto
+ - const: qcom,riva-pil
reg:
maxItems: 3
--
2.37.3
next prev parent reply other threads:[~2022-09-20 3:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 3:03 [PATCH v3 0/4] remoteproc: qcom: Add support for pronto-v3 Sireesh Kodali
2022-09-20 3:03 ` [PATCH v3 1/4] remoteproc: qcom: qcom_wcnss: " Sireesh Kodali
2022-09-20 3:03 ` [PATCH v3 2/4] dt-bindings: remoteproc: qcom: Convert wcnss documentation to YAML Sireesh Kodali
2022-09-20 8:18 ` Krzysztof Kozlowski
2022-09-20 9:54 ` Krzysztof Kozlowski
2022-09-20 3:03 ` Sireesh Kodali [this message]
2022-09-20 9:55 ` [PATCH v3 3/4] dt-bindings: remoteproc: qcom: wcnss: Add qcom,pronto compatible Krzysztof Kozlowski
2022-09-20 3:03 ` [PATCH v3 4/4] dt-bindings: remoteproc: qcom: wcnss: Add compatible for pronto v3 Sireesh Kodali
2022-09-20 9:55 ` Krzysztof Kozlowski
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=20220920030316.1619781-4-sireeshkodali1@gmail.com \
--to=sireeshkodali1@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=robh+dt@kernel.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).