From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: david@ixit.cz, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Richard Acayan <mailingradian@gmail.com>,
Petr Vorel <petr.vorel@gmail.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, phone-devel@vger.kernel.org
Subject: Re: [PATCH RFC 2/4] soc: qcom: Add modemsmem for Google phones
Date: Mon, 7 Sep 2026 10:36:13 +0200 [thread overview]
Message-ID: <b84cb955-2ee4-4865-9bb6-3fec074f451a@oss.qualcomm.com> (raw)
In-Reply-To: <20260906-modemsmem-v1-2-a3634b553841@ixit.cz>
On 9/6/26 2:41 AM, David Heidelberg via B4 Relay wrote:
> From: Richard Acayan <mailingradian@gmail.com>
>
> Modems on Google Pixel devices require extra information about the
> SoC to be passed through a vendor-controlled Shared Memory (SMEM)
> channel. This driver provides this information.
[...]
> + ret = of_property_read_u32(dev->of_node, "qcom,smem-id", &smem_id);
Is it ever not 134?
FWIW you may find this useful:
134 - SMEM_ID_VENDOR0
135 - SMEM_ID_VENDOR1
136 - SMEM_ID_VENDOR2
which you may find in various downstream kernel used for various
purposes
Konrad
next prev parent reply other threads:[~2026-09-07 8:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260906-modemsmem-v1-0-a3634b553841@ixit.cz>
[not found] ` <20260906-modemsmem-v1-4-a3634b553841@ixit.cz>
2026-09-06 0:50 ` [PATCH RFC 4/4] arm64: dts: qcom: sdm670-google: Add modemsmem sashiko-bot
[not found] ` <20260906-modemsmem-v1-3-a3634b553841@ixit.cz>
2026-09-06 0:50 ` [PATCH RFC 3/4] arm64: dts: qcom: sdm845-google: " sashiko-bot
[not found] ` <20260906-modemsmem-v1-2-a3634b553841@ixit.cz>
2026-09-06 0:49 ` [PATCH RFC 2/4] soc: qcom: Add modemsmem for Google phones sashiko-bot
2026-09-07 8:36 ` Konrad Dybcio [this message]
2026-09-07 8:37 ` [PATCH RFC 0/4] " 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=b84cb955-2ee4-4865-9bb6-3fec074f451a@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--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=mailingradian@gmail.com \
--cc=petr.vorel@gmail.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh@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