mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Nyekjaer <sean@geanix.com>
To: Sudarshan Shetty <tessolveupstream@gmail.com>, luca.ceresoli@bootlin.com
Cc: andrzej.hajda@intel.com, neil.armstrong@linaro.org,
	rfoss@kernel.org, Laurent.pinchart@ideasonboard.com,
	jonas@kwiboo.se, jernej.skrabec@gmail.com,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
	alexander.stein@ew.tq-group.com, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] drm: bridge: ti-sn65dsi83: Disable video burst mode for LVDS stability
Date: Sat, 30 May 2026 18:51:42 +0000	[thread overview]
Message-ID: <ahsxWhXMhzbAj_3G@Seans-MacBook-Pro.local> (raw)

Hi Luca,

On Wed, May 27, 2026 at 02:27:36PM +0100, Sudarshan Shetty wrote:
> The current DSI configuration enables MIPI_DSI_MODE_VIDEO_BURST.
> while burst mode is supported by the hardware, its use
> depends on continuous clock behavior from the DSI host. In practice,
> burst mode may introduce instability depending on the host controller
> implementation, as the DSI link may transition to low-power state
> between bursts.
> 
> Testing showed improved display stability when using non-burst mode on
> affected panels.
> 
> Remove MIPI_DSI_MODE_VIDEO_BURST and use non-burst video mode.
> 

We briefly talked about this at Embedded Recipes
I promised to sent a link:
https://lore.kernel.org/all/E35054BA-FBE5-4CEE-905C-1F5D20140590@geanix.com/

When burst mode is enabled, the LVDS clock gets way to high for my
panel. I don't know if it's the DSI controller in the STM32MP1 or
something not supported on the TI side.

We have been running with this fix for 2 years :)

> Tested-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
> Tested-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> Signed-off-by: Sudarshan Shetty <tessolveupstream@gmail.com>

Tested-by: Sean Nyekjaer <sean@geanix.com>

> ---
>  drivers/gpu/drm/bridge/ti-sn65dsi83.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/bridge/ti-sn65dsi83.c b/drivers/gpu/drm/bridge/ti-sn65dsi83.c
> index c03ff1ea9df8..6b5a6019c30d 100644
> --- a/drivers/gpu/drm/bridge/ti-sn65dsi83.c
> +++ b/drivers/gpu/drm/bridge/ti-sn65dsi83.c
> @@ -976,8 +976,8 @@ static int sn65dsi83_host_attach(struct sn65dsi83 *ctx)
>  
>  	dsi->lanes = dsi_lanes;
>  	dsi->format = MIPI_DSI_FMT_RGB888;
> -	dsi->mode_flags = MIPI_DSI_MODE_VIDEO | MIPI_DSI_MODE_VIDEO_BURST |
> -			  MIPI_DSI_MODE_VIDEO_NO_HSA | MIPI_DSI_MODE_NO_EOT_PACKET;
> +	dsi->mode_flags = MIPI_DSI_MODE_VIDEO | MIPI_DSI_MODE_VIDEO_NO_HSA |
> +			  MIPI_DSI_MODE_NO_EOT_PACKET;
>  
>  	ret = devm_mipi_dsi_attach(dev, dsi);
>  	if (ret < 0) {
> -- 
> 2.34.1
> 


             reply	other threads:[~2026-05-30 18:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-30 18:51 Sean Nyekjaer [this message]
2026-06-05 15:18 ` Luca Ceresoli
2026-06-05 16:09   ` Laurent Pinchart
2026-06-05 16:56     ` Luca Ceresoli
2026-06-05 17:31       ` Laurent Pinchart
2026-06-08  6:33         ` Sean Nyekjaer
2026-06-16  8:28         ` Luca Ceresoli
2026-06-16 16:18           ` Maxime Ripard
2026-06-08  7:12       ` Maxime Ripard
2026-06-08  6:37     ` Alexander Stein
2026-06-08  7:09     ` Maxime Ripard
2026-06-08  7:14       ` Laurent Pinchart
2026-06-08  8:59         ` Maxime Ripard
  -- strict thread matches above, loose matches on Subject: below --
2026-05-27  8:57 [PATCH v4 0/2] drm: bridge: ti-sn65dsi83: Fix DSI mode flags for stable LVDS output Sudarshan Shetty
2026-05-27  8:57 ` [PATCH v4 2/2] drm: bridge: ti-sn65dsi83: Disable video burst mode for LVDS stability Sudarshan Shetty

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=ahsxWhXMhzbAj_3G@Seans-MacBook-Pro.local \
    --to=sean@geanix.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=andrzej.hajda@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.ceresoli@bootlin.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=rfoss@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tessolveupstream@gmail.com \
    --cc=tzimmermann@suse.de \
    /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

Powered by JetHome