From: Alex Elder <elder@riscstar.com>
To: Esteban Urrutia <esteuwu@proton.me>,
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, 8 Jul 2026 14:49:09 -0500 [thread overview]
Message-ID: <8309e9c7-a110-478b-8cd4-c002070d2b4c@riscstar.com> (raw)
In-Reply-To: <48c624c3-5408-4862-b4ec-9321ad279bf9@proton.me>
On 6/23/26 8:57 PM, Esteban Urrutia wrote:
> On 6/23/26 11:56 AM, Alex Elder wrote:
>> I assume you have implemented this based on what you found in
>> some downstream code. And if so, could you please indicate
>> where to find that (so I can do some cross-referencing myself).
>> I no longer have access to any Qualcomm internal documentation.
>
> Hello. Yes, that would be the case. What I used goes as follows.
Thank you very much for sharing this information.
> 1. My personal findings regarding IPA:
> https://gist.github.com/esteuwu/bd49ed67ed9290f41612bdae1cacb5bc
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.
> Note that these may be subject to errors since I mostly cross-checked
> values to get here.
>
> 2. SM8450 downstream device tree:
> https://github.com/LineageOS/android_kernel_qcom_sm8450-devicetrees/blob/lineage-20/qcom/waipio.dtsi#L3304
>
> 3. SM8475 downstream device tree:
> https://github.com/LineageOS/android_kernel_qcom_sm8450-devicetrees/blob/lineage-20/qcom/cape.dtsi#L2624
>
> It's worth mentioning that between SM8450 and SM8475, IPA SRAM size is
> different, so I used the smaller SRAM size to support SM8475 as well. Hence
> the reason why I included SM8475's downstream device tree as well.
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.
> 4. SM8450/SM8475 downstream IPA driver:
> https://github.com/LineageOS/android_kernel_qcom_sm8450-modules/tree/lineage-20/qcom/opensource/dataipa
>
> Most of my cross-checking came from the source code in this folder.
Yes, "ipa_utils.c" contains a great deal of the information
needed.
>
> Finally, for some values such as qmap, aggregation, tre_count and
> event_count, I had to cross-check on the same folder that all
> ipa_data-vX.Y.c files reside, since I couldn't find any reference to these
> values in downstream code.
I'll try to explain those things separately.
-Alex
> Regards,
> Esteban
>
next prev parent reply other threads:[~2026-07-08 19:49 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 [this message]
2026-07-08 20:45 ` Esteban Urrutia
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=8309e9c7-a110-478b-8cd4-c002070d2b4c@riscstar.com \
--to=elder@riscstar.com \
--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=esteuwu@proton.me \
--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