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>, Sam Day <me@samcday.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: Re: [PATCH v2 1/5] arm64: dts: qcom: sdm845-xiaomi-beryllium: Introduce framebuffer
Date: Wed, 18 Mar 2026 12:46:34 +0100 [thread overview]
Message-ID: <e5dcf0b9-3a46-4432-bd74-4c509bbf49d7@oss.qualcomm.com> (raw)
In-Reply-To: <20260317-beryllium-fb-v2-1-36b69dfb760c@ixit.cz>
On 3/17/26 11:12 PM, David Heidelberg via B4 Relay wrote:
> 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 01b570d0880d6..b928100f6464b 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: framebuffer-0 {
If you don't expect more framebuffers in the future, just 'framebuffer'
for the name is OK
Konrad
next prev parent reply other threads:[~2026-03-18 11:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 22:12 [PATCH v2 0/5] Add framebuffer on Xiaomi Poco F1 and disable the MDSS on tianma panel variant David Heidelberg via B4 Relay
2026-03-17 22:12 ` [PATCH v2 1/5] arm64: dts: qcom: sdm845-xiaomi-beryllium: Introduce framebuffer David Heidelberg via B4 Relay
2026-03-18 11:46 ` Konrad Dybcio [this message]
2026-03-18 11:46 ` Konrad Dybcio
2026-03-17 22:12 ` [PATCH v2 2/5] arm64: dts: qcom: sdm845-oneplus: Drop address from framebuffer node David Heidelberg via B4 Relay
2026-03-18 14:41 ` Dmitry Baryshkov
2026-03-17 22:12 ` [PATCH v2 3/5] arm64: dts: qcom: sdm845-shift-axolotl: Convert fb to use memory-region David Heidelberg via B4 Relay
2026-03-18 14:41 ` Dmitry Baryshkov
2026-03-17 22:12 ` [PATCH v2 4/5] arm64: dts: qcom: sdm845-samsung-starqltechn: " David Heidelberg via B4 Relay
2026-03-18 14:42 ` Dmitry Baryshkov
2026-03-17 22:12 ` [PATCH v2 5/5] arm64: dts: qcom: sdm845-xiaomi-beryllium-tianma: Disable MDSS David Heidelberg via B4 Relay
2026-03-18 14:47 ` Dmitry Baryshkov
2026-03-18 14:49 ` David Heidelberg
2026-04-10 13:51 ` David Heidelberg
2026-04-12 0:36 ` Dmitry Baryshkov
2026-04-12 9:03 ` David Heidelberg
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=e5dcf0b9-3a46-4432-bd74-4c509bbf49d7@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--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=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