From: <linux@martijnvandeventer.nl>
To: "'Jerome Brunet'" <jbrunet@baylibre.com>, <linux@martijnvandeventer.nl>
Cc: "'Neil Armstrong'" <neil.armstrong@linaro.org>,
"'Michael Turquette'" <mturquette@baylibre.com>,
"'Stephen Boyd'" <sboyd@kernel.org>,
"'Kevin Hilman'" <khilman@baylibre.com>,
"'Martin Blumenstingl'" <martin.blumenstingl@googlemail.com>,
<linux-amlogic@lists.infradead.org>, <linux-clk@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] clk: meson: g12a: Fix kernel warnings when no display attached
Date: Thu, 6 Mar 2025 17:48:33 +0100 [thread overview]
Message-ID: <004801db8eb7$99808e20$cc81aa60$@martijnvandeventer.nl> (raw)
In-Reply-To: <1jplj3g21q.fsf@starbuckisacylon.baylibre.com>
Hi Jerome,
> >
> > Thank you for reviewing, and apologies for my late response due to a
> holiday.
> >
> >> On Thu 13 Feb 2025 at 23:17, Martijn van Deventer
> >> <linux@martijnvandeventer.nl> wrote:
> >>
> >> > When booting SM1 or G12A boards without a dislay attached to HDMI,
> >> > the kernel shows the following warning:
> >> >
> >> > [CRTC:46:meson_crtc] vblank wait timed out
> >> > WARNING: CPU: 2 PID: 265 at
> drivers/gpu/drm/drm_atomic_helper.c:1682
> >> drm_atomic_helper_wait_for_vblanks.part.0+0x240/0x264
> >> > CPU: 2 UID: 0 PID: 265 Comm: setfont Tainted: G C
> >> > Tainted: [C]=CRAP
> >> > pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> >> > pc : drm_atomic_helper_wait_for_vblanks.part.0+0x240/0x264
> >> > lr : drm_atomic_helper_wait_for_vblanks.part.0+0x240/0x264
> >> > Call trace:
> >> > drm_atomic_helper_wait_for_vblanks.part.0+0x240/0x264
> >> > drm_atomic_helper_commit_tail_rpm+0x84/0xa0
> >> > commit_tail+0xa4/0x18c
> >> > drm_atomic_helper_commit+0x164/0x178
> >> > drm_atomic_commit+0xb4/0xec
> >> > drm_client_modeset_commit_atomic+0x210/0x270
> >> > drm_client_modeset_commit_locked+0x5c/0x188
> >> > drm_fb_helper_pan_display+0xb8/0x1d4
> >> > fb_pan_display+0x7c/0x120
> >> > bit_update_start+0x20/0x48
> >> > fbcon_switch+0x418/0x54c
> >> > el0t_64_sync+0x194/0x198
> >> >
> >> > This happens when the kernel disables the unused clocks.
> >> > Sometimes this causes the boot to hang.
> >> >
> >> > By (re)adding the flag CLK_IGNORE_UNUSED to the VCLK2 clocks, these
> >> > clocks will not be disabled.
> >> >
> >> > This partially reverts commit b70cb1a21a54 ("clk: meson: g12a:
> >> > make VCLK2 and ENCL clock path configurable by CCF").
> >>
> >> It looks like DRM needs those clock enabled regardless of connection
> >> status on HDMI. Even with this change applied, you would get the same
> >> problem again if the bootloader does not take of turning the clock on,
> >> which is not a given.
> >>
> >> CLK_IGNORE_UNUSED gives not guarantee a clock will be enabled or stay
> >> enabled at any point.
> >>
> >> A proper fix to this issue should be done in DRM, IMO.
> >
> > I know and I totally agree. Unfortunately, I don't have access to any
> > vendor
> > documentation, nor do I have any real knowledge about the DRM/HDMI
> > subsystem to fix that.
>
> You have identified which clocks are not properly claimed, by what they
> are not claimed and even when. 50% of the job is done. Thanks for this.
You're welcome, no problem.
> >
> > And I guess if it were as easy as adding a clock to the DT and calling
> > clk_prepare_enable on it in the probe function, Neil would have done
> that
> > already.
> >
> > So, all I can do, for now, is revert to the previous situation when it
> > did
> work
> > for (probably) most boards.
>
> Maybe so, but it does not make this change appropriate. The problem
> is the DRM driver which does not enable what it needs to properly
> operate. This should be fixed.
I understand. So I guess that is the end of the line for this patch.
Because this patch will not be accepted and if someone else finds the
time and has the knowledge to fix this the proper way, it will be a
completely different patch.
Although I, of course, agree with you that it should be fixed properly,
I find it a bit difficult to accept that if we accidentally break something,
while trying to make things better, we are not allowed to revert it
because it was already somewhat broken. Resulting in a more broken
situation than before...
On the other hand, I also understand that if you, as a maintainer, allow
that, chances are it will never see a proper fix. :-)
Cheers!
> >
> >> >
> >> > Fixes: b70cb1a21a54 ("clk: meson: g12a: make VCLK2 and ENCL clock
> path
> >> configurable by CCF").
> >> > Signed-off-by: Martijn van Deventer <linux@martijnvandeventer.nl>
> >> > ---
> >> > drivers/clk/meson/g12a.c | 12 ++++++------
> >> > 1 file changed, 6 insertions(+), 6 deletions(-)
> >> >
> >> > diff --git a/drivers/clk/meson/g12a.c b/drivers/clk/meson/g12a.c
> >> > index cfffd434e998..1651898658f5 100644
> >> > --- a/drivers/clk/meson/g12a.c
> >> > +++ b/drivers/clk/meson/g12a.c
> >> > @@ -3234,7 +3234,7 @@ static struct clk_regmap g12a_vclk2_div = {
--
Best regards,
Martijn
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2025-03-06 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 22:17 [PATCH] clk: meson: g12a: Fix kernel warnings when no display attached Martijn van Deventer
2025-02-14 9:08 ` Jerome Brunet
2025-02-26 20:39 ` linux
2025-02-27 9:38 ` Jerome Brunet
2025-03-06 16:48 ` linux [this message]
2025-03-06 17:26 ` Jerome Brunet
2025-03-06 20:13 ` linux
2025-02-14 11:15 ` Neil Armstrong
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='004801db8eb7$99808e20$cc81aa60$@martijnvandeventer.nl' \
--to=linux@martijnvandeventer.nl \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--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