From: Paul Kocialkowski <paulk@sys-base.io>
To: dri-devel@lists.freedesktop.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: "Marek Vasut" <marex@denx.de>, "Stefan Agner" <stefan@agner.ch>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>, "Frank Li" <Frank.Li@nxp.com>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Krzysztof Hałasa" <khalasa@piap.pl>,
"Marco Felsch" <m.felsch@pengutronix.de>,
"Liu Ying" <victor.liu@nxp.com>,
"Paul Kocialkowski" <paulk@sys-base.io>
Subject: [PATCH 2/3] drm: lcdif: Use dedicated set/clr registers for polarity/edge
Date: Tue, 31 Mar 2026 00:46:18 +0200 [thread overview]
Message-ID: <20260330224619.2620782-3-paulk@sys-base.io> (raw)
In-Reply-To: <20260330224619.2620782-1-paulk@sys-base.io>
The lcdif v3 hardware comes with dedicated registers to set and clear
polarity bits in the CTRL register. It is unclear if there is a
difference with writing to the CTRL register directly.
Follow the NXP BSP reference by using these registers, in case there is
a subtle difference caused by using them.
Signed-off-by: Paul Kocialkowski <paulk@sys-base.io>
---
drivers/gpu/drm/mxsfb/lcdif_kms.c | 23 ++++++++++++++++-------
1 file changed, 16 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/mxsfb/lcdif_kms.c b/drivers/gpu/drm/mxsfb/lcdif_kms.c
index a00c4f6d63f4..1aac354041c7 100644
--- a/drivers/gpu/drm/mxsfb/lcdif_kms.c
+++ b/drivers/gpu/drm/mxsfb/lcdif_kms.c
@@ -296,18 +296,27 @@ static void lcdif_set_formats(struct lcdif_drm_private *lcdif,
static void lcdif_set_mode(struct lcdif_drm_private *lcdif, u32 bus_flags)
{
struct drm_display_mode *m = &lcdif->crtc.state->adjusted_mode;
- u32 ctrl = 0;
+ u32 ctrl;
if (m->flags & DRM_MODE_FLAG_NHSYNC)
- ctrl |= CTRL_INV_HS;
+ writel(CTRL_INV_HS, lcdif->base + LCDC_V8_CTRL + REG_SET);
+ else
+ writel(CTRL_INV_HS, lcdif->base + LCDC_V8_CTRL + REG_CLR);
+
if (m->flags & DRM_MODE_FLAG_NVSYNC)
- ctrl |= CTRL_INV_VS;
+ writel(CTRL_INV_VS, lcdif->base + LCDC_V8_CTRL + REG_SET);
+ else
+ writel(CTRL_INV_VS, lcdif->base + LCDC_V8_CTRL + REG_CLR);
+
if (bus_flags & DRM_BUS_FLAG_DE_LOW)
- ctrl |= CTRL_INV_DE;
- if (bus_flags & DRM_BUS_FLAG_PIXDATA_DRIVE_NEGEDGE)
- ctrl |= CTRL_INV_PXCK;
+ writel(CTRL_INV_DE, lcdif->base + LCDC_V8_CTRL + REG_SET);
+ else
+ writel(CTRL_INV_DE, lcdif->base + LCDC_V8_CTRL + REG_CLR);
- writel(ctrl, lcdif->base + LCDC_V8_CTRL);
+ if (bus_flags & DRM_BUS_FLAG_PIXDATA_DRIVE_NEGEDGE)
+ writel(CTRL_INV_PXCK, lcdif->base + LCDC_V8_CTRL + REG_SET);
+ else
+ writel(CTRL_INV_PXCK, lcdif->base + LCDC_V8_CTRL + REG_CLR);
writel(DISP_SIZE_DELTA_Y(m->vdisplay) |
DISP_SIZE_DELTA_X(m->hdisplay),
--
2.53.0
next prev parent reply other threads:[~2026-03-30 22:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 22:46 [PATCH 0/3] drm: lcdif: FIFO underrun/solid color bug fix Paul Kocialkowski
2026-03-30 22:46 ` [PATCH 1/3] drm: lcdif: Set undocumented bit to clear FIFO at vsync Paul Kocialkowski
2026-03-31 9:07 ` Lucas Stach
2026-03-30 22:46 ` Paul Kocialkowski [this message]
2026-03-31 9:09 ` [PATCH 2/3] drm: lcdif: Use dedicated set/clr registers for polarity/edge Lucas Stach
2026-03-31 15:17 ` Paul Kocialkowski
2026-03-31 16:04 ` Lucas Stach
2026-04-02 16:08 ` Paul Kocialkowski
2026-03-30 22:46 ` [PATCH 3/3] drm: lcdif: Wait for vblank before disabling DMA Paul Kocialkowski
2026-03-31 9:14 ` Lucas Stach
2026-04-02 18:29 ` Paul Kocialkowski
2026-03-31 10:11 ` Krzysztof Hałasa
2026-04-02 16:50 ` Paul Kocialkowski
2026-04-03 4:36 ` Krzysztof Hałasa
2026-04-03 4:43 ` Krzysztof Hałasa
2026-04-04 19:29 ` Paul Kocialkowski
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=20260330224619.2620782-3-paulk@sys-base.io \
--to=paulk@sys-base.io \
--cc=Frank.Li@nxp.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=khalasa@piap.pl \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marex@denx.de \
--cc=mripard@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=simona@ffwll.ch \
--cc=stefan@agner.ch \
--cc=tzimmermann@suse.de \
--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