Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Esben Haabendal <esben@geanix.com>
To: Gary Bisson <bisson.gary@gmail.com>
Cc: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
	 Philipp Zabel <p.zabel@pengutronix.de>,
	 David Airlie <airlied@gmail.com>,
	 Simona Vetter <simona@ffwll.ch>,
	 Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	dri-devel@lists.freedesktop.org,
	 linux-mediatek@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	 linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] drm/mediatek: mtk_dsi: enable hs clock during pre-enable
Date: Wed, 15 Jul 2026 14:53:15 +0200	[thread overview]
Message-ID: <8733xko1ms.fsf@geanix.com> (raw)
In-Reply-To: <20260120-mtkdsi-v1-1-b0f4094f3ac3@gmail.com> (Gary Bisson's message of "Tue, 20 Jan 2026 12:36:59 +0100")

Gary Bisson <bisson.gary@gmail.com> writes:

> Some bridges, such as the TI SN65DSI83, require the HS clock to be
> running in order to lock its PLL during its own pre-enable function.
>
> Without this change, the bridge gives the following error:
> sn65dsi83 14-002c: failed to lock PLL, ret=-110
> sn65dsi83 14-002c: Unexpected link status 0x01
> sn65dsi83 14-002c: reset the pipe
>
> Move the necessary functions from enable to pre-enable.
>
> Signed-off-by: Gary Bisson <bisson.gary@gmail.com>

Hi

I have run into the same problem, but in combination with another
pipeline. I am seeing same problem with an i.MX8 using the nwl-dsi
bridge and the dcss driver.

I have submitted a fix that adresses the problem in the ti-sn65dsi83
driver instead. With a bit of luck, it can replace the fix proposed in
this thread.

See https://lore.kernel.org/all/20260711-ti-sn65dsi83-fixes-v1-2-d85eb5342b98@geanix.com/

/Esben


  parent reply	other threads:[~2026-07-15 12:53 UTC|newest]

Thread overview: 21+ 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 [this message]
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

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=8733xko1ms.fsf@geanix.com \
    --to=esben@geanix.com \
    --cc=airlied@gmail.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=bisson.gary@gmail.com \
    --cc=chunkuang.hu@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --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=p.zabel@pengutronix.de \
    --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