[<prev] [next>] [day] [month] [year] [list]
Message-ID: <8ae33208-3273-4bca-8371-6fc1ef50061f@denx.de>
Date: Tue, 9 Jul 2024 22:25:42 +0200
From: Marek Vasut <marex@...x.de>
To: Stefano Radaelli <stefano.radaelli21@...il.com>
Cc: "Rob Herring (Arm)" <robh@...nel.org>,
Laurent Pinchart <Laurent.pinchart@...asonboard.com>,
Jonas Karlman <jonas@...boo.se>, Andrzej Hajda <andrzej.hajda@...el.com>,
Thomas Zimmermann <tzimmermann@...e.de>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
David Airlie <airlied@...il.com>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Maxime Ripard <mripard@...nel.org>,
Neil Armstrong <neil.armstrong@...aro.org>, Robert Foss <rfoss@...nel.org>,
Jernej Skrabec <jernej.skrabec@...il.com>, devicetree@...r.kernel.org,
dri-devel@...ts.freedesktop.org, Daniel Vetter <daniel@...ll.ch>,
"Noah J . Rosa" <noahj.rosa@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: display: bridge: ti,sn65dsi83: add
burst-mode-disabled
On 7/9/24 7:30 PM, Stefano Radaelli wrote:
> Okay, I get it.
>
> So if you think this mode shouldn't be implemented within this driver, we
> can close the thread.
> Just for information, this driver has been implemented from the work done
> by Compulab (as it says in the driver's initial comments), and they do not
> put the burst mode by default, not even giving the possibility to activate
> it by dts:
> https://github.com/compulab-yokneam/imx8-android/blob/master/o8/vendor/nxp-opensource/kernel_imx/0055-sn65dsi83-Add-ti-sn65dsi83-dsi-to-lvds-bridge-driver.patch
This is not the mainline Linux driver.
> The panels that I've had these problems with are some of JuTouch's
> 1920x1200, for example JT101TM015 , and I solved it by giving the option to
> remove this mode.
> I have also heard from other colleagues who have had the same problem on
> some dual-channel displays.
Does that problem happen with the aforementioned driver or the mainline
Linux driver ?
Powered by blists - more mailing lists