All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Petr Vorel <petr.vorel@gmail.com>, Petr Vorel <pevik@seznam.cz>,
	Dominik Kobinski <dominikkobinski314@gmail.com>
Cc: linux-arm-msm@vger.kernel.org, Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	devicetree@vger.kernel.org, Bart Ribbers <bribbers@disroot.org>,
	Alexey Minnekhanov <alexeymin@postmarketos.org>
Subject: Re: [PATCH 1/1] arm64: dts: qcom: msm8992-lg-bullhead: Disable cont_splash_mem
Date: Mon, 5 Dec 2022 12:09:09 +0100	[thread overview]
Message-ID: <2cf45767-7974-3b40-fa18-ec33db5d5ac2@linaro.org> (raw)
In-Reply-To: <CAB1t1CzmNK8i0qT43qVw7VGUPVi67Up6QU-kYDoEsrV7=N7u7w@mail.gmail.com>



On 04/12/2022 14:16, Petr Vorel wrote:
> Hi all,
> 
> 
> I got reply from Dominik that he noticed dfps_data_mem (reserved in
> msm8994.dtsi) overlaps with the framebuffer region.
They are usually next to each other..

> I'll retest it next week, maybe removing it instead of cont_splash_mem
> fixes the reboot.
Maybe your bootloader reads it? And needs it to be at a certain address,
maybe with a certain node name or a label?

> 
> He also noticed, that Linux doesn't reboot when loaded from uefi (his
> project [1]).
> Not sure if there is any difference.
Is it loaded with this DTB or does it rely on ACPI?

Konrad
> 
> Kind regards,
> Petr
> 
> [1] https://github.com/Dominduchami/Nexus5XPkg/

  reply	other threads:[~2022-12-05 11:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-26  1:05 [PATCH 1/1] arm64: dts: qcom: msm8992-lg-bullhead: Disable cont_splash_mem Petr Vorel
2022-12-04 13:16 ` Petr Vorel
2022-12-05 11:09   ` Konrad Dybcio [this message]
2022-12-05 20:59     ` Dominik Kobinski
2022-12-10  5:24     ` Dominik Kobinski
2022-12-10  9:28       ` Konrad Dybcio
2022-12-10 20:39         ` Petr Vorel

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=2cf45767-7974-3b40-fa18-ec33db5d5ac2@linaro.org \
    --to=konrad.dybcio@linaro.org \
    --cc=agross@kernel.org \
    --cc=alexeymin@postmarketos.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=bribbers@disroot.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dominikkobinski314@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=petr.vorel@gmail.com \
    --cc=pevik@seznam.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.