From: tessolveupstream@gmail.com
To: Luca Ceresoli <luca.ceresoli@bootlin.com>,
andrzej.hajda@intel.com, neil.armstrong@linaro.org,
rfoss@kernel.org
Cc: Laurent.pinchart@ideasonboard.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, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, marex@denx.de, valentin@compulab.co.il,
philippe.schenker@toradex.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
dri-devel <dri-devel-bounces@lists.freedesktop.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: display: bridge: ti, sn65dsi83: Add dual-link video mode property
Date: Wed, 18 Mar 2026 11:19:16 +0530 [thread overview]
Message-ID: <ff819e02-3ecc-4729-9c6f-16c74c2b23cb@gmail.com> (raw)
In-Reply-To: <DH0X5VHW15QI.XOHUGC314J1P@bootlin.com>
On 12-03-2026 21:16, Luca Ceresoli wrote:
> Hello Sudarshan,
>
> On Thu Mar 12, 2026 at 5:37 AM CET, Sudarshan Shetty wrote:
>> Add a new optional device tree property `ti,dual-link-video-mode`
>> to indicate that the bridge should configure the device for
>> dual-link LVDS video mode.
>>
>> In dual-link configurations, some panels require the horizontal
>> timing parameters to be adjusted before programming them into
>> the device. In such cases, the horizontal timing values must be
>> divided by two when operating in dual-link mode.
>>
>> Signed-off-by: Sudarshan Shetty <tessolveupstream@gmail.com>
>
> This is not needed. Dual link mode is already implied by the presence of
> port@2 and port@3.
>
> Also, the driver implements that already, and handles even/odd pixel swap
> as well:
>
> ctx->lvds_dual_link = false;
> ctx->lvds_dual_link_even_odd_swap = false;
> if (model != MODEL_SN65DSI83) {
> struct device_node *port2, *port3;
> int dual_link;
>
> port2 = of_graph_get_port_by_id(dev->of_node, 2);
> port3 = of_graph_get_port_by_id(dev->of_node, 3);
> dual_link = drm_of_lvds_get_dual_link_pixel_order(port2, port3);
> of_node_put(port2);
> of_node_put(port3);
>
> if (dual_link == DRM_LVDS_DUAL_LINK_ODD_EVEN_PIXELS) {
> ctx->lvds_dual_link = true;
> /* Odd pixels to LVDS Channel A, even pixels to B */
> ctx->lvds_dual_link_even_odd_swap = false;
> } else if (dual_link == DRM_LVDS_DUAL_LINK_EVEN_ODD_PIXELS) {
> ctx->lvds_dual_link = true;
> /* Even pixels to LVDS Channel A, odd pixels to B */
> ctx->lvds_dual_link_even_odd_swap = true;
> }
> }
>
> (https://elixir.bootlin.com/linux/v7.0-rc3/source/drivers/gpu/drm/bridge/ti-sn65dsi83.c#L895-L916)
>
Thanks for the clarification.
For reference, the DTS currently used on our platform already
describes the two LVDS output ports as follows:
lvds_bridge: bridge@2c {
compatible = "ti,sn65dsi84";
reg = <0x2c>;
enable-gpios = <&tlmm 42 GPIO_ACTIVE_HIGH>;
ti,dual-link-video-mode;
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
sn65dsi84_in: endpoint {
data-lanes = <1 2 3 4>;
remote-endpoint = <&mdss_dsi0_out>;
};
};
port@2 {
reg = <2>;
sn65dsi84_out_a: endpoint {
data-lanes = <1 2 3 4>;
remote-endpoint = <&lvds_panel_out_a>;
};
};
port@3 {
reg = <3>;
sn65dsi84_out_b: endpoint {
data-lanes = <1 2 3 4>;
remote-endpoint = <&lvds_panel_out_b>;
};
};
};
> Luca
>
> --
> Luca Ceresoli, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
next prev parent reply other threads:[~2026-03-18 5:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 4:37 [PATCH v2 0/2] drm: bridge: ti-sn65dsi83: Improve dual-link LVDS support Sudarshan Shetty
2026-03-12 4:37 ` [PATCH v2 1/2] dt-bindings: display: bridge: ti,sn65dsi83: Add dual-link video mode property Sudarshan Shetty
2026-03-12 15:46 ` [PATCH v2 1/2] dt-bindings: display: bridge: ti, sn65dsi83: " Luca Ceresoli
2026-03-13 8:55 ` Krzysztof Kozlowski
2026-03-18 5:48 ` tessolveupstream
2026-03-18 5:49 ` tessolveupstream [this message]
2026-03-12 4:37 ` [PATCH v2 2/2] drm: bridge: ti-sn65dsi83: Add support for dual-link LVDS video mode Sudarshan Shetty
2026-03-12 15:47 ` Luca Ceresoli
2026-03-18 5:53 ` tessolveupstream
2026-03-18 8:52 ` Luca Ceresoli
2026-03-12 5:05 ` [PATCH v2 0/2] drm: bridge: ti-sn65dsi83: Improve dual-link LVDS support Marek Vasut
2026-03-12 12:35 ` tessolveupstream
2026-03-12 15:49 ` Luca Ceresoli
2026-03-18 5:45 ` tessolveupstream
2026-03-18 8:51 ` Luca Ceresoli
2026-03-19 9:55 ` tessolveupstream
2026-03-19 13:47 ` Luca Ceresoli
2026-03-24 11:00 ` tessolveupstream
2026-03-24 11:10 ` Alexander Stein
2026-03-25 6:09 ` tessolveupstream
2026-03-25 7:14 ` Alexander Stein
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=ff819e02-3ecc-4729-9c6f-16c74c2b23cb@gmail.com \
--to=tessolveupstream@gmail.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel-bounces@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@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=philippe.schenker@toradex.com \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=valentin@compulab.co.il \
/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