From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Igor Belwon <igor.belwon@mentallysanemainliners.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abelvesa@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] arm64: dts: qcom: Add support for Xiaomi 17 Ultra phones
Date: Tue, 20 Oct 2026 15:57:52 +0200 [thread overview]
Message-ID: <e4501d93-7781-405d-b7e3-99d21358d707@oss.qualcomm.com> (raw)
In-Reply-To: <20261019-nezha-v4-2-19c1e31eb255@mentallysanemainliners.org>
On 10/19/26 5:47 PM, Igor Belwon wrote:
> The Xiaomi 17 Ultra device, codenamed 'nezha', is a flagship mobile
> phone released by Xiaomi in 2025 (China)/2026 (EEA). It uses the
> Qualcomm Kaanapali SoC.
Nice!
[...]
> + reserved-memory {
> + /*
> + * If we do not have this exact region with this exact name
> + * present, the bootloader disables the display panel and
> + * for some reason it cannot be re-enabled.
> + */
> + splash_region@fc800000 {
> + reg = <0x0 0xfc800000 0x0 0x2b00000>;
> + no-map;
> + };
> +
> + /delete-node/ pdp@81300000;
> + pdp_mem: pdp@81200000 {
> + reg = <0x0 0x81200000 0x0 0x200000>;
> + no-map;
> + };
Please check if your firmware automatically carves out
0x81200000-0x812fffff
If not, insetad add a cpucp@81200000 node to the DTSI that's
0x100000-long
Konrad
prev parent reply other threads:[~2026-10-20 13:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 15:47 [PATCH v4 0/2] arm64: dts: qcom: Add support for the Xiaomi 17 Ultra series of devices Igor Belwon
2026-10-19 15:47 ` [PATCH v4 1/2] dt-bindings: arm: qcom: Document Xiaomi 17 Ultra devices Igor Belwon
2026-10-19 15:47 ` [PATCH v4 2/2] arm64: dts: qcom: Add support for Xiaomi 17 Ultra phones Igor Belwon
2026-10-20 13:02 ` Abel Vesa
2026-10-20 13:57 ` Konrad Dybcio [this message]
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=e4501d93-7781-405d-b7e3-99d21358d707@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=igor.belwon@mentallysanemainliners.org \
--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
all inboxes | Powered by JetHome®