Devicetree
 help / color / mirror / Atom feed
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 1/4] arm64: dts: qcom: sdm845-xiaomi-beryllium: Introduce framebuffer
Date: Thu, 02 Apr 2026 00:39:35 +0200	[thread overview]
Message-ID: <20260402-beryllium-fb-v4-1-46170004da28@ixit.cz> (raw)
In-Reply-To: <20260402-beryllium-fb-v4-0-46170004da28@ixit.cz>

From: Petr Hodina <petr.hodina@protonmail.com>

Add framebuffer for early console and u-boot support.

Signed-off-by: Petr Hodina <petr.hodina@protonmail.com>
Signed-off-by: David Heidelberg <david@ixit.cz>
---
 .../boot/dts/qcom/sdm845-xiaomi-beryllium-common.dtsi    | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/arch/arm64/boot/dts/qcom/sdm845-xiaomi-beryllium-common.dtsi b/arch/arm64/boot/dts/qcom/sdm845-xiaomi-beryllium-common.dtsi
index 1298485c42142..a6ee3dd171def 100644
--- a/arch/arm64/boot/dts/qcom/sdm845-xiaomi-beryllium-common.dtsi
+++ b/arch/arm64/boot/dts/qcom/sdm845-xiaomi-beryllium-common.dtsi
@@ -39,6 +39,22 @@ aliases {
 		serial1 = &uart6;
 	};
 
+	chosen {
+		#address-cells = <2>;
+		#size-cells = <2>;
+		ranges;
+
+		framebuffer {
+			compatible = "simple-framebuffer";
+			memory-region = <&cont_splash_mem>;
+
+			format = "a8r8g8b8";
+			stride = <(1080 * 4)>;
+			height = <2246>;
+			width = <1080>;
+		};
+	};
+
 	gpio-keys {
 		compatible = "gpio-keys";
 		autorepeat;

-- 
2.53.0



  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 ` David Heidelberg via B4 Relay [this message]
2026-04-02  8:50   ` [PATCH v4 1/4] arm64: dts: qcom: sdm845-xiaomi-beryllium: Introduce framebuffer 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 ` [PATCH v4 3/4] arm64: dts: qcom: sdm845-shift-axolotl: Convert fb to use memory-region David Heidelberg via B4 Relay
2026-04-01 22:39 ` [PATCH v4 4/4] arm64: dts: qcom: sdm845-samsung-starqltechn: " 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-1-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