mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 1/3] dt-bindings: remoteproc: qcom,msm8996-mss-pil: Document google,require-socinfo
Date: Mon, 16 Nov 2026 16:50:43 +0100	[thread overview]
Message-ID: <20261116-modemsmem-v3-1-24ebc7ed6eb9@ixit.cz> (raw)
In-Reply-To: <20261116-modemsmem-v3-0-24ebc7ed6eb9@ixit.cz>

From: David Heidelberg <david@ixit.cz>

The modem firmware on Google Pixel boards (Pixel 3 through Pixel 5a)
expects the application processor to publish the SoC platform type,
subtype and revision in the first vendor-reserved SMEM item before the
modem is started. Represent that requirement as a boolean property on
the MSS remoteproc node so the MSS driver can publish the data before
booting the modem, instead of carrying a separate node and driver for
it.

This patch was written with assistance from a large language model.

Signed-off-by: David Heidelberg <david@ixit.cz>
---
 .../devicetree/bindings/remoteproc/qcom,msm8996-mss-pil.yaml     | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,msm8996-mss-pil.yaml b/Documentation/devicetree/bindings/remoteproc/qcom,msm8996-mss-pil.yaml
index 4a1b439f985e3..ecc6782a92245 100644
--- a/Documentation/devicetree/bindings/remoteproc/qcom,msm8996-mss-pil.yaml
+++ b/Documentation/devicetree/bindings/remoteproc/qcom,msm8996-mss-pil.yaml
@@ -91,16 +91,25 @@ properties:
       - const: mss_restart
       - const: pdc_reset # only valid for qcom,sdm845-mss-pil
     minItems: 1
 
   qcom,qmp:
     $ref: /schemas/types.yaml#/definitions/phandle
     description: Reference to the AOSS side-channel message RAM.
 
+  google,require-socinfo:
+    type: boolean
+    description:
+      The modem firmware on Google Pixel boards (Pixel 3 through Pixel 5a)
+      expects the application processor to publish the SoC platform type,
+      subtype and revision in the first vendor-reserved SMEM item (item 134)
+      before the modem is started. When present, the MSS driver fills that
+      item from the socinfo SMEM data before booting the modem.
+
   qcom,smem-states:
     $ref: /schemas/types.yaml#/definitions/phandle-array
     description: States used by the AP to signal the Hexagon core
     items:
       - description: Stop modem
         items:
           - description: Phandle to the Shared Memory Point 2 Point or Shared
               Memory Manager device handling the communication with a remote

-- 
2.55.0



  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 [PATCH v3 0/3] Add modemsmem for Google phones David Heidelberg via B4 Relay
2026-11-16 15:50 ` David Heidelberg via B4 Relay [this message]
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-1-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®