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: bjorn.andersson@linaro.org,
Sireesh Kodali <sireeshkodali1@gmail.com>,
Andy Gross <agross@kernel.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 v2 3/4] dt-bindings: remoteproc: qcom: wcnss: Add qcom,pronto compatible
Date: Fri, 9 Sep 2022 00:19:24 +0530 [thread overview]
Message-ID: <20220908184925.2714098-4-sireeshkodali1@gmail.com> (raw)
In-Reply-To: <20220908184925.2714098-1-sireeshkodali1@gmail.com>
The qcom,pronto compatible is used in the wcn36xx driver to determine
which register to access. However, this compatible was not documented.
This patch documents the existing compatible as is, since it isn't
immediately clear why the wcn36xx driver uses this extra compatible,
rather than relying directly on the regular compatible string.
Signed-off-by: Sireesh Kodali <sireeshkodali1@gmail.com>
---
.../bindings/remoteproc/qcom,wcnss-pil.yaml | 16 ++++++++++++----
1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,wcnss-pil.yaml b/Documentation/devicetree/bindings/remoteproc/qcom,wcnss-pil.yaml
index bc18139fdb91..5e4a97e9d330 100644
--- a/Documentation/devicetree/bindings/remoteproc/qcom,wcnss-pil.yaml
+++ b/Documentation/devicetree/bindings/remoteproc/qcom,wcnss-pil.yaml
@@ -15,10 +15,18 @@ 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
+ - enum:
+ - qcom,pronto
+ - items:
+ - enum:
+ - qcom,riva-pil
reg:
maxItems: 3
--
2.37.2
next prev parent reply other threads:[~2022-09-08 18:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 18:49 [PATCH v2 0/4] remoteproc: qcom: Add support for pronto-v3 Sireesh Kodali
2022-09-08 18:49 ` [PATCH v2 1/4] remoteproc: qcom: qcom_wcnss: " Sireesh Kodali
2022-09-08 18:49 ` [PATCH v2 2/4] dt-bindings: remoteproc: qcom: Convert wcnss documentation to YAML Sireesh Kodali
2022-09-08 21:16 ` Rob Herring
2022-09-09 8:00 ` Krzysztof Kozlowski
2022-09-12 3:36 ` Sireesh Kodali
2022-09-09 7:57 ` Krzysztof Kozlowski
2022-09-12 3:30 ` Sireesh Kodali
2022-09-09 7:59 ` Krzysztof Kozlowski
2022-09-12 3:37 ` Sireesh Kodali
2022-09-08 18:49 ` Sireesh Kodali [this message]
2022-09-09 8:00 ` [PATCH v2 3/4] dt-bindings: remoteproc: qcom: wcnss: Add qcom,pronto compatible Krzysztof Kozlowski
2022-09-12 3:33 ` Sireesh Kodali
2022-09-12 10:47 ` Krzysztof Kozlowski
2022-09-13 5:02 ` Sireesh Kodali
2022-09-08 18:49 ` [PATCH v2 4/4] dt-bindings: remoteproc: qcom: wcnss: Add compatible for pronto v3 Sireesh Kodali
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=20220908184925.2714098-4-sireeshkodali1@gmail.com \
--to=sireeshkodali1@gmail.com \
--cc=agross@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