Use memory-region property for framebuffer instead of reg.

Signed-off-by: Barnabás Czémán <barnabas.czeman@mainlining.org>
---
 arch/arm64/boot/dts/qcom/sm6125-xiaomi-ginkgo.dts | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/arch/arm64/boot/dts/qcom/sm6125-xiaomi-ginkgo.dts b/arch/arm64/boot/dts/qcom/sm6125-xiaomi-ginkgo.dts
index d5e5abdb3b2f..8497f0cbf819 100644
--- a/arch/arm64/boot/dts/qcom/sm6125-xiaomi-ginkgo.dts
+++ b/arch/arm64/boot/dts/qcom/sm6125-xiaomi-ginkgo.dts
@@ -31,9 +31,9 @@ chosen {
 		#size-cells = <2>;
 		ranges;
 
-		framebuffer0: framebuffer@5c000000 {
+		framebuffer {
 			compatible = "simple-framebuffer";
-			reg = <0 0x5c000000 0 (2340 * 1080 * 4)>;
+			memory-region = <&framebuffer_mem>;
 			width = <1080>;
 			height = <2340>;
 			stride = <(1080 * 4)>;
@@ -62,7 +62,7 @@ gpu_mem: gpu_mem@57515000 {
 			no-map;
 		};
 
-		framebuffer@5c000000 {
+		framebuffer_mem: framebuffer@5c000000 {
 			reg = <0x0 0x5c000000 0x0 (2340 * 1080 * 4)>;
 			no-map;
 		};

-- 
2.52.0

On 1/26/26 5:34 PM, Barnabás Czémán wrote:
> Use memory-region property for framebuffer instead of reg.
> 
> Signed-off-by: Barnabás Czémán <barnabas.czeman@mainlining.org>
> ---

Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>

Konrad