From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Amit Pundir <amit.pundir@linaro.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Konrad Dybcio <konrad.dybcio@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Caleb Connolly <caleb.connolly@linaro.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
dt <devicetree@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: sdm845-db845c: Mark cont splash memory region as reserved
Date: Thu, 9 Feb 2023 11:03:33 +0000 [thread overview]
Message-ID: <b2307e91-3373-539a-ecfb-e2542b9f83db@linaro.org> (raw)
In-Reply-To: <CAMi1Hd2UNxXHUVWO-=sWh=-bVnrqE3UdLguFOq+62SfvUiEs0A@mail.gmail.com>
On 09/02/2023 09:05, Amit Pundir wrote:
> Hi, So what is the verdict on this patch?
>
> I submitted this fix to make sure UFS don't map and crash on it, which
> I have seen happening occassionaly on db845c and Caleb reported
> similar issues on his sdm845 device iirc. I should have probably put
> that in my commit message as well.
>
> Regards,
> Amit Pundir
So the memory _is_ being used by ... continuous splash on an Android
image, i.e. your Android ? limited to Android - image continues on with
the splash but other blocks erroneously reuse the memory then, UFS as an
example ?
---
bod
next prev parent reply other threads:[~2023-02-09 11:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 18:28 [PATCH] arm64: dts: qcom: sdm845-db845c: Mark cont splash memory region as reserved Amit Pundir
2023-01-31 10:46 ` Caleb Connolly
2023-01-31 10:54 ` Bryan O'Donoghue
2023-01-31 11:06 ` Dmitry Baryshkov
2023-01-31 12:45 ` Konrad Dybcio
2023-01-31 13:33 ` Dmitry Baryshkov
2023-02-09 9:05 ` Amit Pundir
2023-02-09 11:03 ` Bryan O'Donoghue [this message]
2023-02-09 12:08 ` Konrad Dybcio
2023-02-09 12:11 ` Bryan O'Donoghue
2023-02-09 12:22 ` Bryan O'Donoghue
2023-02-09 12:32 ` Konrad Dybcio
2023-02-09 13:54 ` Dmitry Baryshkov
2023-04-10 8:51 ` Amit Pundir
2023-04-10 8:54 ` Amit Pundir
2023-04-10 12:44 ` Bryan O'Donoghue
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=b2307e91-3373-539a-ecfb-e2542b9f83db@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=agross@kernel.org \
--cc=amit.pundir@linaro.org \
--cc=andersson@kernel.org \
--cc=caleb.connolly@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).