From: Esteban Urrutia <esteuwu@proton.me>
To: Alex Elder <elder@riscstar.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Alex Elder <elder@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/3] SM8450 IPA support
Date: Wed, 08 Jul 2026 20:45:32 +0000 [thread overview]
Message-ID: <3e70d77e-6bec-4e16-ae88-a4f5161f182e@proton.me> (raw)
In-Reply-To: <8309e9c7-a110-478b-8cd4-c002070d2b4c@riscstar.com>
On 7/8/26 3:49 PM, Alex Elder wrote:
> This was interesting to see. It's something I should probably
> document better. Most everything maps to the downstream code,
> but it's not always completely obvious how, because the upstream
> driver has evolved substantially.
On a personal note, I'm surprised to see someone not from Qualcomm
maintaining this driver. It must be hard, so kudos.
> This means that the SRAM size (ipa_mem_data->smem_size) should
> possibly be defined in devicetree (as the IMEM address and size
> now are).
>
> The SMEM region is used for "IPA filter tables", and access to
> it is shared between the AP and the modem. Unlike the other
> (host) memory regions, the size used is *not* included in the
> ipa_init_modem_driver_req message that communicates from the
> AP to the modem where the regions are, and their sizes.
>
> So it's possible that the size used must actually match what
> is expected by both the AP and modem. If that is the case,
> using the smaller size might have problems on whichever
> platform (SM8450?) expects the larger one.
>
> So I'm not sure whether using the smaller size for both
> platforms is OK; someone from Qualcomm might be able to
> answer that question.
I actually went ahead and reviewed downstream device trees I found on
GitHub (1) which contain both SM8450 and SM8475 device trees looking for
the qcom,ipa-q6-smem-size property, which would correspond to the SRAM
size, and to my surprise, this was set to 0x9000 for both SoCs.
Most likely the commit I got the SRAM information from (2) never made it
to production devices.
With this clarified, I think it should be okay to keep things defined as
they currently are.
> I'll try to explain those things separately.
Regarding this, I have a question: where would this be published?
Thanks for taking the time to properly review my changes.
I'll address the review when I can.
(1) https://github.com/sm8450-mainline/fdt
(2) https://github.com/LineageOS/android_kernel_qcom_sm8450-devicetrees/commit/477aab9e7479ff553c7a162ae74029170a2e8291.patch
Regards,
Esteban
next prev parent reply other threads:[~2026-07-08 20:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 1:44 [PATCH 0/3] SM8450 IPA support Esteban Urrutia via B4 Relay
2026-06-23 1:44 ` [PATCH 1/3] arm64: dts: qcom: sm8450: Add " Esteban Urrutia via B4 Relay
2026-06-23 8:55 ` Krzysztof Kozlowski
2026-06-23 9:37 ` Konrad Dybcio
2026-06-24 1:52 ` Esteban Urrutia
2026-06-29 14:18 ` Konrad Dybcio
2026-06-30 1:57 ` Esteban Urrutia
2026-07-07 10:35 ` Konrad Dybcio
2026-07-07 16:34 ` Esteban Urrutia
2026-06-23 1:44 ` [PATCH 2/3] dt-bindings: net: qcom,ipa: Add SM8450 compatible string Esteban Urrutia via B4 Relay
2026-06-23 8:54 ` Krzysztof Kozlowski
2026-06-23 1:44 ` [PATCH 3/3] net: ipa: Add IPA v5.1 data Esteban Urrutia via B4 Relay
2026-06-24 1:44 ` sashiko-bot
2026-07-08 20:06 ` Alex Elder
2026-07-08 21:35 ` Esteban Urrutia
2026-06-23 15:56 ` [PATCH 0/3] SM8450 IPA support Alex Elder
2026-06-24 1:57 ` Esteban Urrutia
2026-07-08 19:49 ` Alex Elder
2026-07-08 20:45 ` Esteban Urrutia [this message]
2026-07-07 16:45 ` Dmitry Baryshkov
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=3e70d77e-6bec-4e16-ae88-a4f5161f182e@proton.me \
--to=esteuwu@proton.me \
--cc=andersson@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=elder@riscstar.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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