From: David Heidelberg <david@ixit.cz>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: 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>,
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 5/5] arm64: dts: qcom: sdm845-xiaomi-beryllium-tianma: Disable MDSS
Date: Wed, 18 Mar 2026 15:49:49 +0100 [thread overview]
Message-ID: <fa407fff-f3f6-4475-9d21-e713440ff0f8@ixit.cz> (raw)
In-Reply-To: <73fyiqoxxg2gg5244wkukepdfw6lnguq63si22qsx2ueyna4hu@l4vyykvn43oo>
On 18/03/2026 15:47, Dmitry Baryshkov wrote:
> On Tue, Mar 17, 2026 at 11:12:35PM +0100, David Heidelberg via B4 Relay wrote:
>> From: Petr Hodina <petr.hodina@protonmail.com>
>>
>> Currently the panel driver for tianma is broken.
>> Disable MDSS to prevent DRM taking over the framebuffer.
>
> I'd still hope that somebody can get it to work. I'd start by using
> prepare_prev_first. Sumit reported the panel as working in 2020 and I
> have no doubts that it was the case. Another option migt be something
> related to the dispcc (see my [1]).
It's probable that prepare_prev_first will help, just sending the patchas part
of the original series.
I'm completely fine with taking other commits and leaving this one after more
investigation.
David
>
> [1] https://lore.kernel.org/linux-arm-msm/20260217-sdm845-hdk-v1-1-866f1965fef7@oss.qualcomm.com/
>
next prev parent reply other threads:[~2026-03-18 14:49 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
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 [this message]
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=fa407fff-f3f6-4475-9d21-e713440ff0f8@ixit.cz \
--to=david@ixit.cz \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--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