From: Joel Selvaraj <joelselvaraj.oss@gmail.com>
To: Amit Pundir <amit.pundir@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Andy Gross <agross@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Caleb Connolly <caleb.connolly@linaro.org>
Cc: linux-arm-msm <linux-arm-msm@vger.kernel.org>,
dt <devicetree@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
phone-devel <phone-devel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: sdm845-xiaomi-beryllium-tianma: Add reserved memory region
Date: Thu, 26 Jan 2023 00:15:51 -0600 [thread overview]
Message-ID: <b47b5a49-6e68-c827-a88e-f61fb85521c8@gmail.com> (raw)
In-Reply-To: <20230124183257.1525376-1-amit.pundir@linaro.org>
Hi Amit Pundir,
I have a Poco F1 (EBBG) variant and I can confirm that the framebuffer
address is same for the EBBG variant too.
I did a quick check by running the following command based on this link[1]:
xiber:~$ strings /dev/disk/by-partlabel/xbl_a | grep "Display Reserved"
0x9D400000, 0x02400000, "Display Reserved", AddMem, MEM_RES,
SYS_MEM_CAP, Reserv, WRITE_BACK_XN
So I think it's safe to move this to sdm845-xiaomi-beryllium-common.dtsi
Regards,
Joel Selvaraj
[1]
https://wiki.postmarketos.org/wiki/SDM845_Mainlining#Find_the_framebuffer_address
On 24/01/23 12:32, Amit Pundir wrote:
> Put cont splash memory region under the reserved-memory as
> confirmed by the downstream code for Tianma variant as well.
>
> Signed-off-by: Amit Pundir <amit.pundir@linaro.org>
> ---
> This change should probably go in sdm845-xiaomi-beryllium-common but
> I don't have EBBG variant's downstream code nor the device to test.
>
> .../boot/dts/qcom/sdm845-xiaomi-beryllium-tianma.dts | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/sdm845-xiaomi-beryllium-tianma.dts b/arch/arm64/boot/dts/qcom/sdm845-xiaomi-beryllium-tianma.dts
> index 8e176111e599..47cbf725b0e3 100644
> --- a/arch/arm64/boot/dts/qcom/sdm845-xiaomi-beryllium-tianma.dts
> +++ b/arch/arm64/boot/dts/qcom/sdm845-xiaomi-beryllium-tianma.dts
> @@ -7,6 +7,14 @@
> / {
> model = "Xiaomi Pocophone F1 (Tianma)";
> compatible = "xiaomi,beryllium", "qcom,sdm845";
> +
> + reserved-memory {
> + /* Cont splash region set up by the bootloader */
> + cont_splash_mem: framebuffer@9d400000 {
> + reg = <0x0 0x9d400000 0x0 0x2400000>;
> + no-map;
> + };
> + };
> };
>
> &display_panel {
next prev parent reply other threads:[~2023-01-26 6:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 18:32 [PATCH] arm64: dts: qcom: sdm845-xiaomi-beryllium-tianma: Add reserved memory region Amit Pundir
2023-01-26 6:15 ` Joel Selvaraj [this message]
2023-01-27 6:26 ` Amit Pundir
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=b47b5a49-6e68-c827-a88e-f61fb85521c8@gmail.com \
--to=joelselvaraj.oss@gmail.com \
--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=phone-devel@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).