From: Louis Chauvet <louis.chauvet@bootlin.com>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
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>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
Marek Vasut <marex@denx.de>, Linus Walleij <linusw@kernel.org>
Cc: Hui Pu <Hui.Pu@gehealthcare.com>,
Ian Ray <ian.ray@gehealthcare.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] drm/bridge: ti-sn65dsi83: add test pattern generation support
Date: Sun, 26 Apr 2026 00:32:53 +0200 [thread overview]
Message-ID: <d816858f-7891-4724-b0e8-27f4d17afcf0@bootlin.com> (raw)
In-Reply-To: <20260416-ti-sn65dsi83-dual-lvds-fixes-and-test-pattern-v3-1-143886aebc6b@bootlin.com>
On 4/16/26 15:59, Luca Ceresoli wrote:
> Generation of a test pattern output is a useful tool for panel bringup and
> debugging, and very simple to support with this chip.
>
> The value of REG_VID_CHA_ACTIVE_LINE_LENGTH_LOW needs to be divided by two
> for the test pattern to work in dual LVDS mode. While not clearly stated in
> the datasheet, this is needed according to the DSI Tuner [0] output. And
> some dual-LVDS panels refuse to show any picture without this division by
> two.
>
> [0] https://www.ti.com/tool/DSI-TUNER
>
> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
>
Reviewed-by: Louis Chauvet <louis.chauvet@boootlin.com>
> ---
>
> Changes in v3:
> - fixed incorrect halving of hdisplay in single-link mode
>
> Changes in v2:
> - added local variable to avoid potential race condition leading to
> inconsistent settings
> ---
> drivers/gpu/drm/bridge/ti-sn65dsi83.c | 14 ++++++++++++--
> 1 file changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/bridge/ti-sn65dsi83.c b/drivers/gpu/drm/bridge/ti-sn65dsi83.c
> index 17a885244e1e..2b6f6a54edb7 100644
> --- a/drivers/gpu/drm/bridge/ti-sn65dsi83.c
> +++ b/drivers/gpu/drm/bridge/ti-sn65dsi83.c
> @@ -114,6 +114,7 @@
> #define REG_VID_CHA_HORIZONTAL_FRONT_PORCH 0x38
> #define REG_VID_CHA_VERTICAL_FRONT_PORCH 0x3a
> #define REG_VID_CHA_TEST_PATTERN 0x3c
> +#define REG_VID_CHA_TEST_PATTERN_EN BIT(4)
> /* IRQ registers */
> #define REG_IRQ_GLOBAL 0xe0
> #define REG_IRQ_GLOBAL_IRQ_EN BIT(0)
> @@ -134,6 +135,9 @@
> #define REG_IRQ_STAT_CHA_SOT_BIT_ERR BIT(2)
> #define REG_IRQ_STAT_CHA_PLL_UNLOCK BIT(0)
>
> +static bool sn65dsi83_test_pattern;
> +module_param_named(test_pattern, sn65dsi83_test_pattern, bool, 0644);
> +
> enum sn65dsi83_channel {
> CHANNEL_A,
> CHANNEL_B
> @@ -523,6 +527,7 @@ static void sn65dsi83_atomic_pre_enable(struct drm_bridge *bridge,
> const struct drm_display_mode *mode;
> struct drm_connector *connector;
> struct drm_crtc *crtc;
> + bool test_pattern = sn65dsi83_test_pattern;
> bool lvds_format_24bpp;
> bool lvds_format_jeida;
> unsigned int pval;
> @@ -645,7 +650,11 @@ static void sn65dsi83_atomic_pre_enable(struct drm_bridge *bridge,
> REG_LVDS_LANE_CHB_LVDS_TERM : 0));
> regmap_write(ctx->regmap, REG_LVDS_CM, 0x00);
>
> - le16val = cpu_to_le16(mode->hdisplay);
> + /*
> + * Active line length needs to be halved for test pattern
> + * generation in dual LVDS output.
> + */
> + le16val = cpu_to_le16(mode->hdisplay / (test_pattern ? dual_factor : 1));
> regmap_bulk_write(ctx->regmap, REG_VID_CHA_ACTIVE_LINE_LENGTH_LOW,
> &le16val, 2);
> le16val = cpu_to_le16(mode->vdisplay);
> @@ -668,7 +677,8 @@ static void sn65dsi83_atomic_pre_enable(struct drm_bridge *bridge,
> (mode->hsync_start - mode->hdisplay) / dual_factor);
> regmap_write(ctx->regmap, REG_VID_CHA_VERTICAL_FRONT_PORCH,
> mode->vsync_start - mode->vdisplay);
> - regmap_write(ctx->regmap, REG_VID_CHA_TEST_PATTERN, 0x00);
> + regmap_write(ctx->regmap, REG_VID_CHA_TEST_PATTERN,
> + test_pattern ? REG_VID_CHA_TEST_PATTERN_EN : 0);
>
> /* Enable PLL */
> regmap_write(ctx->regmap, REG_RC_PLL_EN, REG_RC_PLL_EN_PLL_EN);
>
next prev parent reply other threads:[~2026-04-25 22:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 13:59 [PATCH v3] drm/bridge: ti-sn65dsi83: two fixes + add test pattern Luca Ceresoli
2026-04-16 13:59 ` [PATCH v3] drm/bridge: ti-sn65dsi83: add test pattern generation support Luca Ceresoli
2026-04-25 22:32 ` Louis Chauvet [this message]
2026-04-22 19:40 ` [PATCH v3] drm/bridge: ti-sn65dsi83: two fixes + add test pattern Dmitry Baryshkov
2026-04-23 7:36 ` Luca Ceresoli
2026-04-23 12:28 ` Dmitry Baryshkov
2026-05-04 10:34 ` Luca Ceresoli
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=d816858f-7891-4724-b0e8-27f4d17afcf0@bootlin.com \
--to=louis.chauvet@bootlin.com \
--cc=Hui.Pu@gehealthcare.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=frieder.schrempf@kontron.de \
--cc=ian.ray@gehealthcare.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marex@denx.de \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=thomas.petazzoni@bootlin.com \
--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
all inboxes | Powered by JetHome®