From: barnabas.czeman@mainlining.org
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: 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>,
Gabriel Gonzales <semfault@disroot.org>,
Kees Cook <kees@kernel.org>, Tony Luck <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
Biswapriyo Nath <nathbappai@gmail.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht, linux@mainlining.org
Subject: Re: [PATCH v2 2/7] arm64: dts: qcom: sm6125-xiaomi-ginkgo: Correct reserved memory ranges
Date: Wed, 21 Jan 2026 15:21:28 +0100 [thread overview]
Message-ID: <90a74369a2c4d9453de733a46fdd0ef1@mainlining.org> (raw)
In-Reply-To: <01d254f7-8c62-4061-ba7e-f358f1904ba5@oss.qualcomm.com>
On 2026-01-21 13:45, Konrad Dybcio wrote:
> On 1/16/26 4:54 PM, Barnabás Czémán wrote:
>> The device was crashing on high memory load because the reserved
>> memory
>> ranges was wrongly defined. Correct the ranges for avoid the crashes.
>> Change the ramoops memory range to match with the values from the
>> recovery
>> to be able to get the results from the device.
>>
>> Fixes: 9b1a6c925c88 ("arm64: dts: qcom: sm6125: Initial support for
>> xiaomi-ginkgo")
>> Signed-off-by: Barnabás Czémán <barnabas.czeman@mainlining.org>
>> ---
>
> Have you verified this new and improved(tm) map e.g. by booting up
> the kernel with memtest=1 in cmdline?
I have verified with cat /dev/zero | tail | sleep 5
I can test with memtest=1 also
>
> Konrad
next prev parent reply other threads:[~2026-01-21 14:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 15:54 [PATCH v2 0/7] Initial Redmi Note 8T support and more Barnabás Czémán
2026-01-16 15:54 ` [PATCH v2 1/7] arm64: dts: qcom: sm6125-xiaomi-ginkgo: Remove board-id Barnabás Czémán
2026-01-16 15:54 ` [PATCH v2 2/7] arm64: dts: qcom: sm6125-xiaomi-ginkgo: Correct reserved memory ranges Barnabás Czémán
2026-01-21 12:45 ` Konrad Dybcio
2026-01-21 14:21 ` barnabas.czeman [this message]
2026-01-21 15:31 ` Konrad Dybcio
2026-01-16 15:54 ` [PATCH v2 3/7] arm64: dts: qcom: sm6125-xiaomi-ginkgo: Set memory-region for framebuffer Barnabás Czémán
2026-01-21 12:46 ` Konrad Dybcio
2026-01-16 15:54 ` [PATCH v2 4/7] arm64: dts: qcom: sm6125-xiaomi-ginkgo: Remove extcon Barnabás Czémán
2026-01-16 15:54 ` [PATCH v2 5/7] arm64: dts: qcom: sm6125-xiaomi-ginkgo: Fix reserved gpio ranges Barnabás Czémán
2026-01-21 12:46 ` Konrad Dybcio
2026-01-16 15:54 ` [PATCH v2 6/7] dt-bindings: arm: qcom: Add Xiaomi Redmi Note 8T Barnabás Czémán
2026-01-16 15:54 ` [PATCH v2 7/7] arm64: dts: qcom: Add " Barnabás Czémán
2026-01-17 2:20 ` [PATCH v2 0/7] Initial Redmi Note 8T support and more Rob Herring
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=90a74369a2c4d9453de733a46fdd0ef1@mainlining.org \
--to=barnabas.czeman@mainlining.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gpiccoli@igalia.com \
--cc=kees@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@mainlining.org \
--cc=nathbappai@gmail.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=semfault@disroot.org \
--cc=tony.luck@intel.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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