From: Sudarshan Shetty <tessolveupstream@gmail.com>
To: andrzej.hajda@intel.com, neil.armstrong@linaro.org
Cc: rfoss@kernel.org, Laurent.pinchart@ideasonboard.com,
tessolveupstream@gmail.com, jonas@kwiboo.se,
jernej.skrabec@gmail.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
simona@ffwll.ch, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] drm: bridge: ti-sn65dsi83: Fix LVDS output configuration
Date: Fri, 3 Oct 2025 14:49:11 +0530 [thread overview]
Message-ID: <20251003091911.3269073-2-tessolveupstream@gmail.com> (raw)
In-Reply-To: <20251003091911.3269073-1-tessolveupstream@gmail.com>
Update the SN65DSI83 bridge driver to improve LVDS output
stability and correctness:
- Program additional device registers during initialization to ensure
proper LVDS configuration.
- Adjust the DSI mode_flags to match the recommended settings.
Both changes are based on guidance from TI SN65DSI83 experts, addressing
cases where the existing driver configuration was insufficient.
Signed-off-by: Sudarshan Shetty <tessolveupstream@gmail.com>
---
drivers/gpu/drm/bridge/ti-sn65dsi83.c | 18 +++++++++++++++---
1 file changed, 15 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/bridge/ti-sn65dsi83.c b/drivers/gpu/drm/bridge/ti-sn65dsi83.c
index 033c44326552..d6a2b20be1fe 100644
--- a/drivers/gpu/drm/bridge/ti-sn65dsi83.c
+++ b/drivers/gpu/drm/bridge/ti-sn65dsi83.c
@@ -613,6 +613,20 @@ static void sn65dsi83_atomic_pre_enable(struct drm_bridge *bridge,
mode->hsync_start - mode->hdisplay);
regmap_write(ctx->regmap, REG_VID_CHA_VERTICAL_FRONT_PORCH,
mode->vsync_start - mode->vdisplay);
+
+ regmap_write(ctx->regmap, 0x0A, 0x05);
+ regmap_write(ctx->regmap, 0x0D, 0x00);
+ regmap_write(ctx->regmap, 0x12, 0x53);
+ regmap_write(ctx->regmap, 0x18, 0x6f);
+ regmap_write(ctx->regmap, 0x19, 0x00);
+ regmap_write(ctx->regmap, 0x24, 0x00);
+ regmap_write(ctx->regmap, 0x25, 0x00);
+ regmap_write(ctx->regmap, 0x2c, 0x10);
+ regmap_write(ctx->regmap, 0x34, 0x28);
+ regmap_write(ctx->regmap, 0x36, 0x00);
+ regmap_write(ctx->regmap, 0x38, 0x00);
+ regmap_write(ctx->regmap, 0x3A, 0x00);
+
regmap_write(ctx->regmap, REG_VID_CHA_TEST_PATTERN, 0x00);
/* Enable PLL */
@@ -912,9 +926,7 @@ static int sn65dsi83_host_attach(struct sn65dsi83 *ctx)
dsi->lanes = dsi_lanes;
dsi->format = MIPI_DSI_FMT_RGB888;
- dsi->mode_flags = MIPI_DSI_MODE_VIDEO | MIPI_DSI_MODE_VIDEO_BURST |
- MIPI_DSI_MODE_VIDEO_NO_HFP | MIPI_DSI_MODE_VIDEO_NO_HBP |
- MIPI_DSI_MODE_VIDEO_NO_HSA | MIPI_DSI_MODE_NO_EOT_PACKET;
+ dsi->mode_flags = MIPI_DSI_MODE_VIDEO;
ret = devm_mipi_dsi_attach(dev, dsi);
if (ret < 0) {
--
2.34.1
next prev parent reply other threads:[~2025-10-03 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 9:19 [PATCH] drm: bridge: ti-sn65dsi83: Fix LVDS output configuration Sudarshan Shetty
2025-10-03 9:19 ` Sudarshan Shetty [this message]
2025-10-14 6:08 ` Sudarshan Shetty
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=20251003091911.3269073-2-tessolveupstream@gmail.com \
--to=tessolveupstream@gmail.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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