From: Jingzhou Zhu <newwheatzjz@zohomail.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sdm850-huawei-matebook-e-2019: Correct ipa_fw_mem for the driver to load successfully
Date: Wed, 10 Dec 2025 10:41:27 +0800 [thread overview]
Message-ID: <3393067.44csPzL39Z@debian-vmware> (raw)
In-Reply-To: <vlz4zg6wnxvxz2hqpzinzxztghwxmx2wwkxl4ami42aqvdjkg5@7o4fvadz76cv>
On Wednesday, 10 December 2025 07:08:41 CST, Dmitry Baryshkov wrote:
> On Mon, Dec 08, 2025 at 11:15:11AM +0800, Jingzhou Zhu wrote:
> > The ipa driver refuses to load with the old ipa_fw_mem in newer kernels.
> > Shrinking its size to 0x5a000 fixes the problem.
> >
> > Fixes: aab69794b55d ("arm64: dts: qcom: Add support for Huawei MateBook E 2019")
> >
> > Signed-off-by: Jingzhou Zhu <newwheatzjz@zohomail.com>
>
> There should be no empty lines between tags.
>
Understood.
> > ---
> > arch/arm64/boot/dts/qcom/sdm850-huawei-matebook-e-2019.dts | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/arch/arm64/boot/dts/qcom/sdm850-huawei-matebook-e-2019.dts b/arch/arm64/boot/dts/qcom/sdm850-huawei-matebook-e-2019.dts
> > index a5f025ae7dbe..f04865381870 100644
> > --- a/arch/arm64/boot/dts/qcom/sdm850-huawei-matebook-e-2019.dts
> > +++ b/arch/arm64/boot/dts/qcom/sdm850-huawei-matebook-e-2019.dts
> > @@ -144,12 +144,12 @@ wlan_msa_mem: wlan-msa@8c400000 {
> > };
> >
> > ipa_fw_mem: ipa-fw@8df00000 {
> > - reg = <0 0x8df00000 0 0x100000>;
> > + reg = <0 0x8df00000 0 0x5a000>;
> > no-map;
> > };
> >
> > - gpu_mem: gpu@97900000 {
> > - reg = <0 0x97900000 0 0x5000>;
> > + gpu_mem: gpu@8df5a000 {
>
> Why are you adjusting gpu_mem?
>
In sdm845.dtsi, ipa_fw_mem is followed by gpu_mem, so I moved gpu_mem to
0x8df5a000 since the memory was freed after shrinking ipa_fw_mem size.
I'm not sure whether the order matters, but I think it's best to follow
how they are arranged in sdm845.dtsi.
Also, this change didn't seem to cause problems according to my testing.
> > + reg = <0 0x8df5a000 0 0x5000>;
> > no-map;
> > };
> >
>
>
next prev parent reply other threads:[~2025-12-10 2:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 3:15 [PATCH 0/2] arm64: dts: qcom: sdm850-huawei-matebook-e-2019: Fix reserved-memory issues to enable IPA Jingzhou Zhu
2025-12-08 3:15 ` [PATCH 1/2] arm64: dts: qcom: sdm850-huawei-matebook-e-2019: Remove duplicate reserved-memroy nodes Jingzhou Zhu
2025-12-09 23:05 ` Dmitry Baryshkov
2025-12-08 3:15 ` [PATCH 2/2] arm64: dts: qcom: sdm850-huawei-matebook-e-2019: Correct ipa_fw_mem for the driver to load successfully Jingzhou Zhu
2025-12-09 23:08 ` Dmitry Baryshkov
2025-12-10 2:41 ` Jingzhou Zhu [this message]
2026-01-05 14:07 ` [PATCH 0/2] arm64: dts: qcom: sdm850-huawei-matebook-e-2019: Fix reserved-memory issues to enable IPA Bjorn Andersson
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=3393067.44csPzL39Z@debian-vmware \
--to=newwheatzjz@zohomail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@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