Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Bisson <bisson.gary@gmail.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	Chun-Kuang Hu <chunkuang.hu@kernel.org>,
	Esben Haabendal <esben@geanix.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	dri-devel@lists.freedesktop.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Adam Thiede <me@adamthiede.com>,
	Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [PATCH] drm/mediatek: mtk_dsi: enable hs clock during pre-enable
Date: Mon, 27 Jul 2026 14:48:30 +0200	[thread overview]
Message-ID: <amdTnudq48tZUTG2@owl5> (raw)
In-Reply-To: <b26a4890-12e9-4995-a71d-d0b7458b1570@leemhuis.info>

Hi Thorsten,

On Mon, Jul 27, 2026 at 02:28:56PM +0200, Thorsten Leemhuis wrote:
> [top-posting to facilitate]
> 
> Gary, Angelo, what's the status here? It looks like this fell through
> the cracks -- or was this issue fixed in between somehow? If yes: great!
> If not: Would be good to finally resolve this, as we are long past "fix
> within a week" rule of thumb from Linus:
> https://www.kernel.org/doc/html/latest/process/handling-regressions.html#on-how-quickly-regressions-should-be-fixed

Not much happened I'm afraid. The status as I see is:
- this patch is necessary to have TI SN65DSI83 working
- this patch also follows the DRM guidelines saying that HS clock must
  be enabled during pre_enable (see previous answer / [1])
- this patch has been successfully tested against MIPI-DSI panels (by
  Angelo) and LVDS panels via TI bridge (by myself)
- Adam reported an issue with another bridge (PS8640) where resume is
  broken
- Esben offered a patch to the TI bridge that would fix the issue we
  were seeing in the first place.

But for the last two points, I'm not sure this calls for a revert yet:
- enabling HS clock in pre_enable still is what should be done [1]
- maybe the issue Adam is facing is due to the bridge driver instead as
  it could not be reproduced with another setup
- Esben patch would break the SN65DSI83 init sequence, suggesting that
  the culprit really is the MIPI bridge for not following the HS clock
  requirement in pre_enable instead [2]

So if we agree on the fact that HS clock must be set during pre_enable
then I don't see a reason to revert that commit.

Regards,
Gary

[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/drm_bridge.c#n169
[2] https://patchwork.kernel.org/project/dri-devel/patch/20260711-ti-sn65dsi83-fixes-v1-2-d85eb5342b98@geanix.com/


  reply	other threads:[~2026-07-27 12:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 11:36 [PATCH] drm/mediatek: mtk_dsi: enable hs clock during pre-enable Gary Bisson
2026-02-25  6:20 ` CK Hu (胡俊光)
2026-02-25  8:20   ` Chen-Yu Tsai
2026-02-25 13:16   ` AngeloGioacchino Del Regno
2026-03-22 12:48 ` Chun-Kuang Hu
2026-06-18 21:06 ` Adam Thiede
2026-06-22 11:22   ` Gary Bisson
2026-06-22 13:23     ` Adam Thiede
2026-07-06 10:16       ` Thorsten Leemhuis
2026-07-07  2:20         ` CK Hu (胡俊光)
2026-07-07  8:51           ` Thorsten Leemhuis
2026-07-07 10:38             ` AngeloGioacchino Del Regno
2026-07-08  1:25               ` Adam Thiede
2026-07-08 12:12                 ` AngeloGioacchino Del Regno
2026-07-08 12:13                 ` Gary Bisson
2026-07-08 12:25                   ` AngeloGioacchino Del Regno
2026-07-15 12:53 ` Esben Haabendal
2026-07-15 13:25   ` AngeloGioacchino Del Regno
2026-07-15 13:36     ` Gary Bisson
2026-07-15 13:40       ` AngeloGioacchino Del Regno
2026-07-15 13:52         ` Esben Haabendal
2026-07-17 16:06           ` Gary Bisson
2026-07-27 12:28             ` Thorsten Leemhuis
2026-07-27 12:48               ` Gary Bisson [this message]
2026-07-27 12:52                 ` Adam Thiede
2026-07-27 14:23                 ` Thorsten Leemhuis
2026-07-27 15:54                   ` AngeloGioacchino Del Regno
2026-07-27 16:34                     ` Adam Thiede

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=amdTnudq48tZUTG2@owl5 \
    --to=bisson.gary@gmail.com \
    --cc=airlied@gmail.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=chunkuang.hu@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=esben@geanix.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=me@adamthiede.com \
    --cc=p.zabel@pengutronix.de \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=simona@ffwll.ch \
    /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