From: David Heidelberg via B4 Relay <devnull+david.ixit.cz@kernel.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>,
Sibi Sankar <sibi.sankar@oss.qualcomm.com>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abelvesa@kernel.org>, Miro Mraz <mraz.miro@seznam.cz>
Cc: Richard Acayan <mailingradian@gmail.com>,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
phone-devel@vger.kernel.org, David Heidelberg <david@ixit.cz>
Subject: [PATCH v3 0/3] Add modemsmem for Google phones
Date: Mon, 16 Nov 2026 16:50:42 +0100 [thread overview]
Message-ID: <20261116-modemsmem-v3-0-24ebc7ed6eb9@ixit.cz> (raw)
The modem on the Pixel 3 family will not come up without the SoC
information Google's downstream kernel publishes in SMEM item 134.
This is the upstream version, modelled per review feedback as a
property of the modem remoteproc node rather than a standalone node
and driver.
This replaces the standalone drivers/soc/qcom/modemsmem driver from
the previous revision: per review feedback the requirement is better
modelled as a property of the modem remoteproc node, with the
conditional snippet in the remoteproc driver.
Changes in v2:
- Represent the requirement as a "google,require-socinfo" property on
the MSS remoteproc node instead of a standalone node and driver.
(Bjorn)
- Move the SMEM publish code into the qcom_q6v5_mss remoteproc driver,
gated by the property. (Bjorn)
- Hard-code SMEM item id 134, no qcom,smem-id property. (Bjorn, Konrad)
- Drop the RFC prefix.
- Link to v1: https://patch.msgid.link/20260906-modemsmem-v1-0-a3634b553841@ixit.cz
---
David Heidelberg (3):
dt-bindings: remoteproc: qcom,msm8996-mss-pil: Document google,require-socinfo
remoteproc: qcom_q6v5_mss: Publish socinfo for Pixel modems
arm64: dts: qcom: sdm845-google: Require modem socinfo
.../bindings/remoteproc/qcom,msm8996-mss-pil.yaml | 9 +++
arch/arm64/boot/dts/qcom/sdm845-google-common.dtsi | 2 +
drivers/remoteproc/qcom_q6v5_mss.c | 75 ++++++++++++++++++++++
3 files changed, 86 insertions(+)
---
base-commit: aaa2f954c21b205a0bcd0961e5b2be4e82e58455
change-id: 20260906-modemsmem-9a1dc1070f7b
Best regards,
--
David Heidelberg <david@ixit.cz>
next reply other threads:[~2026-11-16 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 15:50 David Heidelberg via B4 Relay [this message]
2026-11-16 15:50 ` [PATCH v3 1/3] dt-bindings: remoteproc: qcom,msm8996-mss-pil: Document google,require-socinfo David Heidelberg via B4 Relay
2026-11-16 15:50 ` [PATCH v3 2/3] remoteproc: qcom_q6v5_mss: Publish socinfo for Pixel modems David Heidelberg via B4 Relay
2026-11-16 15:50 ` [PATCH v3 3/3] arm64: dts: qcom: sdm845-google: Require modem socinfo David Heidelberg via B4 Relay
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=20261116-modemsmem-v3-0-24ebc7ed6eb9@ixit.cz \
--to=devnull+david.ixit.cz@kernel.org \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@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=mailingradian@gmail.com \
--cc=mathieu.poirier@linaro.org \
--cc=mraz.miro@seznam.cz \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sibi.sankar@oss.qualcomm.com \
/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
all inboxes | Powered by JetHome®