From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Sireesh Kodali <sireeshkodali1@gmail.com>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-remoteproc@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Cc: andersson@kernel.org, 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>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 4/4] dt-bindings: remoteproc: qcom: wcnss: Add compatible for pronto v3
Date: Tue, 20 Sep 2022 11:55:40 +0200 [thread overview]
Message-ID: <47d939e7-a0e1-84ea-e37a-b95ba7e6810b@linaro.org> (raw)
In-Reply-To: <20220920030316.1619781-5-sireeshkodali1@gmail.com>
On 20/09/2022 05:03, Sireesh Kodali wrote:
> The pronto v3 remoteproc is similar to pronto v2. It is found on the
> MSM8953 platform, which is used by SDM450, SDM625, SDM626, APQ8053 and
> other SoCs. Since the configuration is same on all SoCs, a single
> compatible is used.
>
> Signed-off-by: Sireesh Kodali <sireeshkodali1@gmail.com>
It's a v3. What are the changes?
Best regards,
Krzysztof
prev parent reply other threads:[~2022-09-20 9:55 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 ` [PATCH v3 3/4] dt-bindings: remoteproc: qcom: wcnss: Add qcom,pronto compatible Sireesh Kodali
2022-09-20 9:55 ` 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 [this message]
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=47d939e7-a0e1-84ea-e37a-b95ba7e6810b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--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=sireeshkodali1@gmail.com \
--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).