From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Simon Horman <horms@kernel.org>, Konrad Dybcio <konradybcio@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@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>,
Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 3/3] net: ipa: Grab IMEM slice base/size from DTS
Date: Fri, 23 May 2025 20:16:26 +0200 [thread overview]
Message-ID: <d0b2f237-b4a6-4ce0-95ea-4bf5f3be10e0@oss.qualcomm.com> (raw)
In-Reply-To: <20250523131744.GU365796@horms.kernel.org>
On 5/23/25 3:17 PM, Simon Horman wrote:
> On Fri, May 23, 2025 at 01:08:34AM +0200, Konrad Dybcio wrote:
>> From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>>
>> This is a detail that differ per chip, and not per IPA version (and
>> there are cases of the same IPA versions being implemented across very
>> very very different SoCs).
>>
>> This region isn't actually used by the driver, but we most definitely
>> want to iommu-map it, so that IPA can poke at the data within.
>>
>> Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>
> It looks like these patches are for net-next. For future reference,
> it's best to note that in the subject.
>
> Subject: [PATCH net-next 3/3 v2] ...
>
>> ---
ah, the networking guys and their customs ;)
[...]
>> ret = ipa_imem_init(ipa, mem_data->imem_addr, mem_data->imem_size);
>
> I think you also need to update this line to use the local
> variables imem_addr and imem_size.
I paid great attention to validate that the data I got was good and printed
the value inside the first if branch.. but failed to change it here. Thanks
for catching it!
Konrad
next prev parent reply other threads:[~2025-05-23 18:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 23:08 [PATCH 0/3] Grab IPA IMEM slice through DT Konrad Dybcio
2025-05-22 23:08 ` [PATCH 1/3] dt-bindings: sram: qcom,imem: Allow modem-tables Konrad Dybcio
2025-05-23 17:59 ` Alex Elder
2025-05-23 18:13 ` Konrad Dybcio
2025-05-22 23:08 ` [PATCH 2/3] dt-bindings: net: qcom,ipa: Add sram property for describing IMEM slice Konrad Dybcio
2025-05-23 17:59 ` Alex Elder
2025-05-22 23:08 ` [PATCH 3/3] net: ipa: Grab IMEM slice base/size from DTS Konrad Dybcio
2025-05-23 5:49 ` Dmitry Baryshkov
2025-05-23 13:17 ` Simon Horman
2025-05-23 18:16 ` Konrad Dybcio [this message]
2025-05-23 17:59 ` Alex Elder
2025-05-23 18:59 ` kernel test robot
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=d0b2f237-b4a6-4ce0-95ea-4bf5f3be10e0@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.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=horms@kernel.org \
--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=marijn.suijten@somainline.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