From: David Heidelberg via B4 Relay <devnull+david.ixit.cz@kernel.org>
To: 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>,
David Heidelberg <david@ixit.cz>, Sam Day <me@samcday.com>,
Dzmitry Sankouski <dsankouski@gmail.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org,
Petr Hodina <petr.hodina@protonmail.com>
Subject: [PATCH v4 3/4] arm64: dts: qcom: sdm845-shift-axolotl: Convert fb to use memory-region
Date: Thu, 02 Apr 2026 00:39:37 +0200 [thread overview]
Message-ID: <20260402-beryllium-fb-v4-3-46170004da28@ixit.cz> (raw)
In-Reply-To: <20260402-beryllium-fb-v4-0-46170004da28@ixit.cz>
From: David Heidelberg <david@ixit.cz>
Instead of manually specifying reg, reuse the memory region.
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Signed-off-by: David Heidelberg <david@ixit.cz>
---
arch/arm64/boot/dts/qcom/sdm845-shift-axolotl.dts | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/sdm845-shift-axolotl.dts b/arch/arm64/boot/dts/qcom/sdm845-shift-axolotl.dts
index 740eb22550724..88d970268e282 100644
--- a/arch/arm64/boot/dts/qcom/sdm845-shift-axolotl.dts
+++ b/arch/arm64/boot/dts/qcom/sdm845-shift-axolotl.dts
@@ -23,7 +23,7 @@ / {
qcom,board-id = <11 0>;
aliases {
- display0 = &framebuffer0;
+ display0 = &framebuffer;
serial0 = &uart9;
serial1 = &uart6;
};
@@ -36,9 +36,9 @@ chosen {
stdout-path = "serial0";
/* Use framebuffer setup by the bootloader. */
- framebuffer0: framebuffer@9d400000 {
+ framebuffer: framebuffer {
compatible = "simple-framebuffer";
- reg = <0x0 0x9d400000 0x0 (1080 * 2160 * 4)>;
+ memory-region = <&framebuffer_mem>;
width = <1080>;
height = <2160>;
stride = <(1080 * 4)>;
@@ -62,7 +62,7 @@ key-vol-up {
};
reserved-memory {
- framebuffer@9d400000 {
+ framebuffer_mem: framebuffer@9d400000 {
reg = <0x0 0x9d400000 0x0 (1080 * 2160 * 4)>;
no-map;
};
--
2.53.0
next prev parent reply other threads:[~2026-04-01 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 22:39 [PATCH v4 0/4] Add framebuffer on Xiaomi Poco F1 and disable the MDSS on tianma panel variant David Heidelberg via B4 Relay
2026-04-01 22:39 ` [PATCH v4 1/4] arm64: dts: qcom: sdm845-xiaomi-beryllium: Introduce framebuffer David Heidelberg via B4 Relay
2026-04-02 8:50 ` Konrad Dybcio
2026-04-01 22:39 ` [PATCH v4 2/4] arm64: dts: qcom: sdm845-oneplus: Drop address from framebuffer node David Heidelberg via B4 Relay
2026-04-01 22:39 ` David Heidelberg via B4 Relay [this message]
2026-04-01 22:39 ` [PATCH v4 4/4] arm64: dts: qcom: sdm845-samsung-starqltechn: Convert fb to use memory-region David Heidelberg via B4 Relay
2026-05-07 20:34 ` [PATCH v4 0/4] Add framebuffer on Xiaomi Poco F1 and disable the MDSS on tianma panel variant Bjorn Andersson
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=20260402-beryllium-fb-v4-3-46170004da28@ixit.cz \
--to=devnull+david.ixit.cz@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dsankouski@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@samcday.com \
--cc=petr.hodina@protonmail.com \
--cc=phone-devel@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