linux-kernel - Re: [PATCH RFC] arm64: dts: qcom: sdm845: add framebuffer reserved memory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5c1948b7-aa3b-4c60-acf7-64a138450d57@oss.qualcomm.com>
Date: Tue, 18 Nov 2025 13:26:17 +0100
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: david@...t.cz, Bjorn Andersson <andersson@...nel.org>,
        Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley <conor+dt@...nel.org>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Casey Connolly <casey.connolly@...aro.org>
Subject: Re: [PATCH RFC] arm64: dts: qcom: sdm845: add framebuffer reserved
 memory

On 11/17/25 1:27 PM, David Heidelberg via B4 Relay wrote:
> From: Casey Connolly <casey.connolly@...aro.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@...aro.org>
> Signed-off-by: David Heidelberg <david@...t.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