From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: david@ixit.cz, Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@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,
Casey Connolly <casey.connolly@linaro.org>
Subject: Re: [PATCH RFC] arm64: dts: qcom: sdm845: add framebuffer reserved memory
Date: Tue, 18 Nov 2025 13:26:17 +0100 [thread overview]
Message-ID: <5c1948b7-aa3b-4c60-acf7-64a138450d57@oss.qualcomm.com> (raw)
In-Reply-To: <20251117-commonize-framebuffer-v1-1-e4c099b383c9@ixit.cz>
On 11/17/25 1:27 PM, David Heidelberg via B4 Relay wrote:
> From: Casey Connolly <casey.connolly@linaro.org>
>
> Stick it with the other default reserved regions, all sdm845 devices
> use this address except for cheza.
>
> Signed-off-by: Casey Connolly <casey.connolly@linaro.org>
> Signed-off-by: David Heidelberg <david@ixit.cz>
> ---
> What do you think about this proposed change?
>
> I assume QCOM recommends or by default use the default memory region,
> but as can be seen on cheza or sdm850, it seems that vendor can customize
> the region, thus it's not guranteed to have it always on the same address.
>
> There are two approaches I see:
> 1. keep as is defined in each device-tree frambuffer node
> 2. commonize frambuffer node to sdm845.dtsi and in case of exception
> remove the node and definite it in device-tree.
Generally this carveout is useful only if you use the bootloader-
initiated framebuffer. Post that, drm/msm allocates its own
Konrad
next prev parent reply other threads:[~2025-11-18 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 12:27 David Heidelberg via B4 Relay
2025-11-18 12:26 ` Konrad Dybcio [this message]
2025-11-18 12:54 ` Dmitry Baryshkov
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=5c1948b7-aa3b-4c60-acf7-64a138450d57@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=casey.connolly@linaro.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.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®