From: sashiko-bot@kernel.org
To: "Esben Haabendal" <esben@geanix.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 3/3] drm/bridge: ti-sn65dsi83: Support LVDS Channel B on SN65DSI84
Date: Wed, 15 Jul 2026 13:18:23 +0000 [thread overview]
Message-ID: <20260715131824.544FE1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260715-ti-sn65dsi83-fixes-v2-3-ebc4c3fe29b6@geanix.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The logic to detect single-link LVDS Channel B requires `port@2` to be absent from the device tree, but the DT binding strictly requires `port@2` to be present.
--
--- Patch [3]: [PATCH v2 3/3] drm/bridge: ti-sn65dsi83: Support LVDS Channel B on SN65DSI84 ---
commit e7655ab4d66cbec701adf0102160008944fa2a88
Author: Esben Haabendal <esben@geanix.com>
drm/bridge: ti-sn65dsi83: Support LVDS Channel B on SN65DSI84
This adds support for using SN65DSI84 in single-link mode with output to
LVDS Channel B.
> diff --git a/drivers/gpu/drm/bridge/ti-sn65dsi83.c b/drivers/gpu/drm/bridge/ti-sn65dsi83.c
> index 7e73035d77986..02ae2b8179b07 100644
> --- a/drivers/gpu/drm/bridge/ti-sn65dsi83.c
> +++ b/drivers/gpu/drm/bridge/ti-sn65dsi83.c
[ ... ]
> @@ -904,29 +907,38 @@ static int sn65dsi83_parse_dt(struct sn65dsi83 *ctx, enum sn65dsi83_model model)
> return ret;
>
> ctx->lvds_dual_link = false;
> - ctx->lvds_dual_link_even_odd_swap = false;
> + ctx->lvds_channel_swap = false;
> if (model != MODEL_SN65DSI83) {
> - struct device_node *port2, *port3;
> + struct device_node *port0, *port1, *port2, *port3;
> int dual_link;
>
> + port0 = of_graph_get_port_by_id(dev->of_node, 0);
> + port1 = of_graph_get_port_by_id(dev->of_node, 1);
> 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);
>
> if (dual_link == DRM_LVDS_DUAL_LINK_ODD_EVEN_PIXELS) {
> /* Odd pixels to LVDS Channel A, even pixels to B */
> ctx->lvds_dual_link = true;
> } else if (dual_link == DRM_LVDS_DUAL_LINK_EVEN_ODD_PIXELS) {
> /* Even pixels to LVDS Channel A, odd pixels to B */
> ctx->lvds_dual_link = true;
> + ctx->lvds_channel_swap = true;
> + } else if (port0 && !port1 && port2 && !port3) {
> + /* DSI Channel A to LVDS Channel A */
> + } else if (port0 && !port1 && !port2 && port3) {
^^^^^^
[Severity: Medium]
Will this !port2 condition prevent the single-link LVDS Channel B feature
from working with a standard-compliant device tree?
If a user provides a compliant device tree by including an empty or
unconnected port@2 to satisfy the DT schema required list for this binding,
of_graph_get_port_by_id() will return a valid node.
The driver would then fail this check, fall through leaving panel_port = 2,
and subsequently fail to probe when it cannot find a panel connected to the
empty port@2.
> + /* DSI Channel A to LVDS Channel B */
> + ctx->lvds_channel_swap = true;
> + panel_port = 3;
> }
> + of_node_put(port0);
> + of_node_put(port1);
> + of_node_put(port2);
> + of_node_put(port3);
> }
>
> - panel_bridge = devm_drm_of_get_bridge(dev, dev->of_node, 2, 0);
> + panel_bridge = devm_drm_of_get_bridge(dev, dev->of_node, panel_port, 0);
> if (IS_ERR(panel_bridge))
> return dev_err_probe(dev, PTR_ERR(panel_bridge), "Failed to get panel bridge\n");
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260715-ti-sn65dsi83-fixes-v2-0-ebc4c3fe29b6@geanix.com?part=3
prev parent reply other threads:[~2026-07-15 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 13:10 [PATCH v2 0/3] drm/bridge: ti-sn65dsi83: Various fixes Esben Haabendal
2026-07-15 13:10 ` [PATCH v2 1/3] drm/bridge: ti-sn65dsi83: Fix problem with premature PLL locking Esben Haabendal
2026-07-15 13:32 ` sashiko-bot
2026-07-15 13:10 ` [PATCH v2 2/3] drm/bridge: ti-sn65dsi83: Fix error handling in sn65dsi83_reset_work() Esben Haabendal
2026-07-15 13:21 ` sashiko-bot
2026-07-15 13:10 ` [PATCH v2 3/3] drm/bridge: ti-sn65dsi83: Support LVDS Channel B on SN65DSI84 Esben Haabendal
2026-07-15 13:18 ` sashiko-bot [this message]
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=20260715131824.544FE1F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=esben@geanix.com \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.