From: Marek Vasut <marex@denx.de>
To: Liu Ying <victor.liu@nxp.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Cc: andrzej.hajda@intel.com, narmstrong@baylibre.com,
robert.foss@linaro.org, Laurent.pinchart@ideasonboard.com,
jonas@kwiboo.se, jernej.skrabec@gmail.com, airlied@linux.ie,
daniel@ffwll.ch, sam@ravnborg.org, linux-imx@nxp.com
Subject: Re: [PATCH 3/3] drm/bridge: fsl-ldb: Drop DE signal polarity inversion
Date: Fri, 1 Jul 2022 10:03:18 +0200 [thread overview]
Message-ID: <66b6ed2f-a2db-e02d-503f-5bc736c4ee57@denx.de> (raw)
In-Reply-To: <20220701065634.4027537-4-victor.liu@nxp.com>
On 7/1/22 08:56, Liu Ying wrote:
> It's unnecessary to invert input data enable signal polarity
> according to the output one. Let's drop the inversion.
> Since ->atomic_check() does nothing more than the inversion,
> it can be dropped entirely as well.
>
> Without this patch, 'koe,tx26d202vm0bwa' LVDS panel connected
> with i.MX8MP EVK board does not show any data on screen.
I send exactly the same change yesterday:
[PATCH] drm: bridge: ldb: Drop DE flip from Freescale i.MX8MP LDB bridge
So either can be applied.
Reviewed-by: Marek Vasut <marex@denx.de>
next prev parent reply other threads:[~2022-07-01 11:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 6:56 [PATCH 0/3] drm/bridge: fsl-ldb: A few fixes Liu Ying
2022-07-01 6:56 ` [PATCH 1/3] drm/bridge: fsl-ldb: Fix mode clock rate validation Liu Ying
2022-07-01 8:02 ` Marek Vasut
2022-07-06 13:34 ` Robert Foss
2022-07-07 8:12 ` Neil Armstrong
2022-07-01 6:56 ` [PATCH 2/3] drm/bridge: fsl-ldb: Enable split mode for LVDS dual link Liu Ying
2022-07-01 8:02 ` Marek Vasut
2022-07-01 6:56 ` [PATCH 3/3] drm/bridge: fsl-ldb: Drop DE signal polarity inversion Liu Ying
2022-07-01 8:03 ` Marek Vasut [this message]
2022-07-04 14:24 ` [PATCH 0/3] drm/bridge: fsl-ldb: A few fixes Neil Armstrong
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=66b6ed2f-a2db-e02d-503f-5bc736c4ee57@denx.de \
--to=marex@denx.de \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=robert.foss@linaro.org \
--cc=sam@ravnborg.org \
--cc=victor.liu@nxp.com \
/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
all inboxes | Powered by JetHome®