From: "Barnabás Czémán" <barnabas.czeman@mainlining.org>
To: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Stephan Gerhold <stephan@gerhold.net>
Cc: linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Barnabás Czémán" <barnabas.czeman@mainlining.org>
Subject: [PATCH v2 0/9] MDM9607/MSM8917/MSM8937/MSM8940 MSS
Date: Wed, 31 Dec 2025 03:29:27 +0100 [thread overview]
Message-ID: <20251231-mss-v2-0-ae5eafd835c4@mainlining.org> (raw)
This patch series add support for MDM9607/MSM8917/MSM8937/MSM8940 mss.
Signed-off-by: Barnabás Czémán <barnabas.czeman@mainlining.org>
---
Changes in v2:
- qcom_q6v5_mss:
- Intorduce need_pas_mem_setup flag
- Use mss-supply as a regulator for MSM8917, MSM8937 and MSM8940.
- qcom,msm8916-mss-pil:
- Add compatibles where they needed
- Adjust mss-supply description
- Link to v1: https://lore.kernel.org/r/20251228-mss-v1-0-aeb36b1f7a3f@mainlining.org
---
Barnabás Czémán (8):
remoteproc: qcom_q6v5_mss: Introduce need_pas_mem_setup
dt-bindings: remoteproc: qcom,msm8916-mss-pil: Add MDM9607
dt-bindings: remoteproc: qcom,msm8916-mss-pil: Add MSM8917
remoteproc: qcom_q6v5_mss: Add MSM8917
dt-bindings: remoteproc: qcom,msm8916-mss-pil: Add MSM8937
remoteproc: qcom_q6v5_mss: Add MSM8937
dt-bindings: remoteproc: qcom,msm8916-mss-pil: Add MSM8940
remoteproc: qcom_q6v5_mss: Add MSM8940
Stephan Gerhold (1):
remoteproc: qcom_q6v5_mss: Add MDM9607
.../bindings/remoteproc/qcom,msm8916-mss-pil.yaml | 13 +-
drivers/remoteproc/qcom_q6v5_mss.c | 235 ++++++++++++++++++++-
2 files changed, 239 insertions(+), 9 deletions(-)
---
base-commit: cc3aa43b44bdb43dfbac0fcb51c56594a11338a8
change-id: 20251228-mss-1fa61b7092b5
Best regards,
--
Barnabás Czémán <barnabas.czeman@mainlining.org>
next reply other threads:[~2025-12-31 2:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 2:29 Barnabás Czémán [this message]
2025-12-31 2:29 ` [PATCH v2 1/9] remoteproc: qcom_q6v5_mss: Introduce need_pas_mem_setup Barnabás Czémán
2025-12-31 2:29 ` [PATCH v2 2/9] dt-bindings: remoteproc: qcom,msm8916-mss-pil: Add MDM9607 Barnabás Czémán
2025-12-31 2:29 ` [PATCH v2 3/9] remoteproc: qcom_q6v5_mss: " Barnabás Czémán
2025-12-31 12:27 ` Konrad Dybcio
2025-12-31 14:50 ` barnabas.czeman
2025-12-31 15:04 ` Konrad Dybcio
2025-12-31 2:29 ` [PATCH v2 4/9] dt-bindings: remoteproc: qcom,msm8916-mss-pil: Add MSM8917 Barnabás Czémán
2025-12-31 2:29 ` [PATCH v2 5/9] remoteproc: qcom_q6v5_mss: " Barnabás Czémán
2025-12-31 2:29 ` [PATCH v2 6/9] dt-bindings: remoteproc: qcom,msm8916-mss-pil: Add MSM8937 Barnabás Czémán
2025-12-31 2:29 ` [PATCH v2 7/9] remoteproc: qcom_q6v5_mss: " Barnabás Czémán
2025-12-31 2:29 ` [PATCH v2 8/9] dt-bindings: remoteproc: qcom,msm8916-mss-pil: Add MSM8940 Barnabás Czémán
2025-12-31 2:29 ` [PATCH v2 9/9] remoteproc: qcom_q6v5_mss: " Barnabás Czémán
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=20251231-mss-v2-0-ae5eafd835c4@mainlining.org \
--to=barnabas.czeman@mainlining.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.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@kernel.org \
--cc=stephan@gerhold.net \
/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