From: Konrad Dybcio <firstname.lastname@example.org>
To: Petr Vorel <email@example.com>, firstname.lastname@example.org
Cc: Alexey Minnekhanov <email@example.com>,
Andy Gross <firstname.lastname@example.org>,
Bjorn Andersson <email@example.com>,
Rob Herring <firstname.lastname@example.org>,
Subject: Re: [PATCH v2 1/1] arm64: dts: qcom: msm8994-angler: Fix cont_splash_mem
Date: Tue, 22 Jun 2021 20:29:32 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
Ah yes, I think I know the issue..
Angler's firmware (probably Huawei's job, but unsure) seems to make IOMMUs (another guesstimate)
not report where the memory is allocated. If it's an issue only on these boards, I reckon
it would be better to just add
in angler/bullhead DTSI, as other 8992/4 devices seem to not have this issue. But as I've said, bullhead could
probably work anyway, but if it doesn't, it's probably Google's job after all..
I did not suggest redefining the node, as the memory@0 is reserved for SoC registers
and your firmware is just playing tricks on you. Your RAM starts @ 0x80000000.
next prev parent reply other threads:[~2021-06-22 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 18:10 [PATCH v2 1/1] arm64: dts: qcom: msm8994-angler: Fix cont_splash_mem Petr Vorel
2021-06-22 18:29 ` Konrad Dybcio [this message]
2021-06-22 18:43 ` Petr Vorel
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).