[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZoB1ac1bEI8aH-Yp@titan>
Date: Sun, 30 Jun 2024 06:58:17 +1000
From: John Watts <contact@...kia.org>
To: Kirby Nankivell <kirby.nankivell@...il.com>
Cc: Jakob L <jakobl.gm.g@...il.com>, linux-sunxi@...ts.linux.dev,
andre.przywara@....com, Paul Kocialkowski <contact@...lk.fr>,
Maxime Ripard <mripard@...nel.org>, Chen-Yu Tsai <wens@...e.org>,
Jernej Skrabec <jernej.skrabec@...il.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...il.com>, Daniel Vetter <daniel@...ll.ch>,
Samuel Holland <samuel@...lland.org>,
dri-devel@...ts.freedesktop.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: T113 TCON Top tinting troubleshooting
Hi,
On Sat, Jun 29, 2024 at 12:14:39PM +1000, Kirby Nankivell wrote:
> Tested this on a MangoPI-MQ-R with a RGB lcd and can confirm that this fix
> removes the green tint I experienced.
>
> Disabling the mixer1 in DTS entirely also works.
>
> I suspect on the basis that the Mixer/TCON-TOP topology is identical to the
> R40 but does not seem to experience this issue, that is a
> silicon errata specific to the T113/D1s as far as we currently know.
>
> However, there is no functional reason from a drm perspective to require
> more than one mixer tied to one output via tcon-top - unless someone has a
> good argument here?
>
> in my opinion:
> 1) implement this as a quirk on the t113 and fix mixer0 > rgb/dsi and
> mixer1 > tv0
> 2) make this a global default for the sun8i tcon top driver where only one
> mixer is initialised against an output (which would also impact the R40)
The only reason I caught this issue was because I implemented LCD output in
U-Boot and saw it looked a little better- I thought the tint was the backlight.
Had you not contacted me and had it not affected the person I'm doing
work for I would not have bothered looking in to this.
It's entirely possible that the other supported devices have this issue,
or that future ones will and nobody will notice.
Going with a preventative approach here by fixing it for all potential devices
and relying on the behaviour the sunxi code assumes rather than the datasheet
says seems like the best approach to me.
John.
Powered by blists - more mailing lists