From: Parthiban <parthiban@linumiz.com>
To: John Watts <contact@jookia.org>
Cc: parthiban@linumiz.com, Andre Przywara <andre.przywara@arm.com>,
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-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/sun4i: Workaround TCON TOP conflict between DE0 and DE1
Date: Fri, 29 Nov 2024 09:43:55 +0530 [thread overview]
Message-ID: <fa7dbac4-592e-44f9-b468-834779fdbbc2@linumiz.com> (raw)
In-Reply-To: <ZzRgP7-hHWE8JH8K@titan>
On 11/13/24 1:45 PM, John Watts wrote:
> It really seems like the code means mixers here.
True, I was wrong about my statement. But with A133, the case of independent DE
is unique, which I couldn't test yet.
> If my thoughts are correct, this would break use of mixer0 and mixer1 at the
> same time.
Agreed. But back to the original discussion about setting 0x20 to the port
register, it work fine in my end without that changes for A133 display pipeline
with LVDS. Not sure if the reason is independent DE.
Thanks,
Parthiban
prev parent reply other threads:[~2024-11-29 4:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 1:40 [PATCH] drm/sun4i: Workaround TCON TOP conflict between DE0 and DE1 John Watts
2024-11-08 11:53 ` Andre Przywara
2024-11-08 13:29 ` John Watts
2024-11-08 14:06 ` Parthiban
2024-11-08 14:15 ` John Watts
2024-11-12 11:57 ` John Watts
2024-11-12 17:13 ` Parthiban
2024-11-12 23:33 ` John Watts
2024-11-13 6:10 ` Parthiban
2024-11-13 8:15 ` John Watts
2024-11-29 4:13 ` Parthiban [this message]
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=fa7dbac4-592e-44f9-b468-834779fdbbc2@linumiz.com \
--to=parthiban@linumiz.com \
--cc=airlied@gmail.com \
--cc=andre.przywara@arm.com \
--cc=contact@jookia.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@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