From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: 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>,
Manivannan Sadhasivam <mani@kernel.org>
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: [PATCH v4 0/3] SM6375 remoteprocs
Date: Tue, 25 Jul 2023 11:00:27 +0200 [thread overview]
Message-ID: <20230725-topic-6375_rproc-v4-0-d55e8a6d0f5f@linaro.org> (raw)
Resending as the previous revision was mostly ignored on the rproc side.
Changes since v3:
- Pick up krzk's rb on bindings
- Drop patch 4 (applied)
Link to v3: https://lore.kernel.org/linux-arm-msm/20230109135647.339224-1-konrad.dybcio@linaro.org/
This revision merges two [1] [2] previously separate series,
adding SM6375's ADSP, CDSP, MPSS and related bindings.
[1] https://lore.kernel.org/linux-arm-msm/20230107120623.1903056-1-konrad.dybcio@linaro.org/T/#m89d629bd788593dfd27e4dbf0cf0bf94ffd0a7ce
[2] https://lore.kernel.org/linux-arm-msm/622afd8b-a469-4c95-d2b8-030e47b0cac2@linaro.org/T/#m17aee8f3a51cfbd3f92fe2b4dd48b3722a6a0a7e
Konrad Dybcio (4):
dt-bindings: remoteproc: qcom,sm6375-pas: Document remoteprocs
remoteproc: qcom: pas: Add SM6375 ADSP & CDSP
remoteproc: qcom: pas: Add SM6375 MPSS
arm64: dts: qcom: sm6375: Add missing power-domain-named to CDSP
.../bindings/remoteproc/qcom,sm6375-pas.yaml | 137 ++++++++++++++++++
arch/arm64/boot/dts/qcom/sm6375.dtsi | 1 +
drivers/remoteproc/qcom_q6v5_pas.c | 18 +++
3 files changed, 156 insertions(+)
create mode 100644 Documentation/devicetree/bindings/remoteproc/qcom,sm6375-pas.yaml
--
2.39.0
---
Konrad Dybcio (3):
dt-bindings: remoteproc: qcom,sm6375-pas: Document remoteprocs
remoteproc: qcom: pas: Add SM6375 ADSP & CDSP
remoteproc: qcom: pas: Add SM6375 MPSS
.../bindings/remoteproc/qcom,sm6375-pas.yaml | 137 +++++++++++++++++++++
drivers/remoteproc/qcom_q6v5_pas.c | 18 +++
2 files changed, 155 insertions(+)
---
base-commit: 1e25dd7772483f477f79986d956028e9f47f990a
change-id: 20230725-topic-6375_rproc-4f074a92fa5f
Best regards,
--
Konrad Dybcio <konrad.dybcio@linaro.org>
next reply other threads:[~2023-07-25 9:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 9:00 Konrad Dybcio [this message]
2023-07-25 9:00 ` [PATCH v4 1/3] dt-bindings: remoteproc: qcom,sm6375-pas: Document remoteprocs Konrad Dybcio
2023-07-25 9:27 ` Rob Herring
2023-07-26 17:17 ` Krzysztof Kozlowski
2023-07-25 9:00 ` [PATCH v4 2/3] remoteproc: qcom: pas: Add SM6375 ADSP & CDSP Konrad Dybcio
2023-07-25 9:00 ` [PATCH v4 3/3] remoteproc: qcom: pas: Add SM6375 MPSS Konrad Dybcio
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=20230725-topic-6375_rproc-v4-0-d55e8a6d0f5f@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mani@kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=mathieu.poirier@linaro.org \
--cc=robh+dt@kernel.org \
/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).