From: John Watts <contact@jookia.org>
To: Jakob L <jakobl.gm.g@gmail.com>
Cc: linux-sunxi@lists.linux.dev, andre.przywara@arm.com,
"K. James" <kirby.nankivell@gmail.com>,
Paul Kocialkowski <contact@paulk.fr>,
Maxime Ripard <mripard@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Samuel Holland <samuel@sholland.org>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: T113 TCON Top tinting troubleshooting
Date: Sat, 29 Jun 2024 12:12:30 +1000 [thread overview]
Message-ID: <Zn9tjooo9f-oe_3h@titan> (raw)
In-Reply-To: <CALP2yXcUrCdzyqQx7RQUup3QjfbH4VnMVCPFVXNmmd08GJkKMQ@mail.gmail.com>
On Sat, Jun 29, 2024 at 01:49:53AM +0200, Jakob L wrote:
> Hi John,
>
> good find! This seems to fix it on my DSI implementation. Every of the
> recent boots resulted in a pink tint (usually it was green for me, or blue)
> Booted 10 times - no tint.
>
> So this patch is good, but probably has to be implemented as a quirk?
>
> Jakob
Hi Jakob,
I'm not sure if this needs to be a quirk: There's not really a reason to
set both DEs to the same output. My thinking right now is to error in
this situation.
However I think we have to somehow track which DEs have been set so we
can pretend they start unset. For example:
DE0: (Unset, LCD0) DE1: (Unset, TVE0)
Setting DE0 to LCD0 should work, then setting DE1 to LCD0 should fail.
Setting DE0 to LCD0 should work, then setting DE0 to TVE0 should work.
Setting DE0 to TVE0 should work, then setting DE1 to TVE0 should fail.
The mechanism here for setting a DE I think would go like this:
1. Check the opposite DE's value
2. If it is duplicate and set, error
3. If it is duplicate and unset, change the opposite DE's value
4. Set the DE
5. Mark it as set
Step three requires finding an unused DE value, this could be done by
inverting the bits of the new DE. Alternatively we could do what
Allwinner does and start with both DEs at different values and the move
instead the current DE value to the opposite DE to avoid conflicts.
'Set' here may make more sense as 'used'.
I'm good at mentally over-engineering things, so if you can think of a
better solution please tell me.
John.
next prev parent reply other threads:[~2024-06-29 2:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 18:52 T113 TCON Top tinting troubleshooting John Watts
[not found] ` <CALP2yXcUrCdzyqQx7RQUup3QjfbH4VnMVCPFVXNmmd08GJkKMQ@mail.gmail.com>
2024-06-29 2:12 ` John Watts [this message]
[not found] ` <CAMBcuYNG6n1_yc0-5MSFoh2xCfh3-tHG7VcQq5vY65RKSq39RA@mail.gmail.com>
2024-06-29 20:58 ` John Watts
2024-07-02 15:32 ` Jakob L
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=Zn9tjooo9f-oe_3h@titan \
--to=contact@jookia.org \
--cc=airlied@gmail.com \
--cc=andre.przywara@arm.com \
--cc=contact@paulk.fr \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jakobl.gm.g@gmail.com \
--cc=jernej.skrabec@gmail.com \
--cc=kirby.nankivell@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=samuel@sholland.org \
--cc=tzimmermann@suse.de \
--cc=wens@csie.org \
/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;
as well as URLs for NNTP newsgroup(s).