From: "Jérôme de Bretagne" <jerome.debretagne@gmail.com>
To: mitltlatltl@gmail.com
Cc: andersson@kernel.org, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
mturquette@baylibre.com, sboyd@kernel.org,
johannes.goede@oss.qualcomm.com
Subject: Re: [PATCH] clk: qcom: dispcc-sc8280xp: Don't park mdp_clk_src at registration time
Date: Tue, 12 May 2026 19:02:51 +0200 [thread overview]
Message-ID: <20260512170257.8920-1-jerome.debretagne@gmail.com> (raw)
In-Reply-To: <20260303150152.90685-1-mitltlatltl@gmail.com>
> Parking disp{0,1}_cc_mdss_mdp_clk_src clk broke simplefb on HUAWEI
> Gaokun3, the image will stuck at grey for seconds until msm takes
> over framebuffer. Use clk_rcg2_shared_no_init_park_ops to skip it.
>
> Signed-off-by: Pengyu Luo <mitltlatltl@gmail.com>
This patch allows to keep the built-in display enabled on the Microsoft
Surface Pro 9 5G (Arcata) using efifb and software rendering. This was
achieved by passing the "module_blacklist=msm" option. It is really
useful as the built-in display is not yet working thus not described
in the arcata devicetree so far.
Thank you Pengyu.
Tested-by: Jérôme de Bretagne <jerome.debretagne@gmail.com>
Without this patch, the initial EFI framebuffer gets disabled a few
seconds after the initial boot messages. This has been a regression
as it used to work when doing the initial bringup with Linux 6.9.
As mentioned in the similar patchset for the x1e80100 dispcc driver
https://lore.kernel.org/all/67a51928-1c16-48a6-ac65-f67c36297e5e@oss.qualcomm.com/
according to Hans, this should be a fix for the following commit:
Fixes: 01a0a6cc8cfd ("clk: qcom: Park shared RCGs upon registration")
Regards,
Jérôme
parent reply other threads:[~2026-05-12 17:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260303150152.90685-1-mitltlatltl@gmail.com>]
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=20260512170257.8920-1-jerome.debretagne@gmail.com \
--to=jerome.debretagne@gmail.com \
--cc=andersson@kernel.org \
--cc=johannes.goede@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mitltlatltl@gmail.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@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