All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Laurentiu Palcu" <laurentiu.palcu@oss.nxp.com>
Cc: conor+dt@kernel.org, linux-clk@vger.kernel.org,
	dri-devel@lists.freedesktop.org, Frank.Li@kernel.org,
	devicetree@vger.kernel.org, imx@lists.linux.dev, robh@kernel.org
Subject: Re: [PATCH v10 2/9] drm/bridge: fsl-ldb: Get the next non-panel bridge
Date: Tue, 06 Oct 2026 12:30:43 +0000	[thread overview]
Message-ID: <20261006123043.84A911F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261006-dcif-upstreaming-v10-2-bcfb28de0aae@oss.nxp.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] commit message: code and commit message mismatch
--

commit e12c6082d93fb0f1838677a94386e1a971817862
Author: Liu Ying <victor.liu@nxp.com>

drm/bridge: fsl-ldb: Get the next non-panel bridge

This commit refactors the fsl-ldb driver to support getting either a panel
bridge or a non-panel bridge as the next bridge in the chain.

> The next bridge in bridge chain could be a panel bridge or a non-panel
> bridge.  Use devm_drm_of_get_bridge() to replace the combination
> function calls of of_drm_find_panel() and devm_drm_panel_bridge_add()
> to get either a panel bridge or a non-panel bridge, instead of getting
> a panel bridge only.

[Severity: Medium]
Is this description accurate for the changes implemented in this patch?

The commit message explicitly claims that devm_drm_of_get_bridge() was used
to replace of_drm_find_panel() and devm_drm_panel_bridge_add(). However,
looking at the diff below, the actual code replaces
of_drm_find_and_get_bridge() with of_drm_get_bridge_by_endpoint() in
fsl_ldb_probe().

Neither devm_drm_of_get_bridge() nor the combination of of_drm_find_panel()
and devm_drm_panel_bridge_add() are present in the previous code or the new
diff.

Could the commit message be updated to accurately reflect the actual API
changes being made?

> diff --git a/drivers/gpu/drm/bridge/fsl-ldb.c b/drivers/gpu/drm/bridge/fsl-ldb.c
> index 7ec84c81cd786..52ae7f5b63c7c 100644
> --- a/drivers/gpu/drm/bridge/fsl-ldb.c
> +++ b/drivers/gpu/drm/bridge/fsl-ldb.c

[ ... ]

> @@ -339,10 +336,14 @@ static int fsl_ldb_probe(struct platform_device *pdev)
>  	if (of_property_present(dev->of_node, "nxp,enable-termination-resistor"))
>  		fsl_ldb->use_termination_resistor = true;
>  
> -	fsl_ldb->bridge.next_bridge = of_drm_find_and_get_bridge(panel_node);
> -	of_node_put(panel_node);
> -	if (!fsl_ldb->bridge.next_bridge)
> -		return -ENODEV;
> +	next_bridge = of_drm_get_bridge_by_endpoint(dev->of_node,
> +						    fsl_ldb->ch0_enabled ? 1 : 2,
> +						    0);
> +	if (IS_ERR(next_bridge))
> +		return dev_err_probe(dev, PTR_ERR(next_bridge),
> +				     "failed to get next bridge\n");
> +
> +	fsl_ldb->bridge.next_bridge = next_bridge;

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261006-dcif-upstreaming-v10-0-bcfb28de0aae@oss.nxp.com?part=2

  reply	other threads:[~2026-10-06 12:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06 12:21 [PATCH v10 0/9] Add support for i.MX94 DCIF Laurentiu Palcu
2026-10-06 12:21 ` [PATCH v10 1/9] dt-bindings: display: fsl,ldb: Add i.MX94 LDB Laurentiu Palcu
2026-10-06 12:21 ` [PATCH v10 2/9] drm/bridge: fsl-ldb: Get the next non-panel bridge Laurentiu Palcu
2026-10-06 12:30   ` sashiko-bot [this message]
2026-10-06 12:21 ` [PATCH v10 3/9] drm/bridge: fsl-ldb: Add support for i.MX94 Laurentiu Palcu
2026-10-06 12:21 ` [PATCH v10 4/9] dt-bindings: display: imx: Add i.MX94 DCIF Laurentiu Palcu
2026-10-06 12:22 ` [PATCH v10 5/9] drm/imx: Add support for " Laurentiu Palcu
2026-10-06 12:39   ` sashiko-bot
2026-10-12 11:18   ` Uwe Kleine-König
2026-10-06 12:22 ` [PATCH v10 6/9] dt-bindings: clock: nxp,imx95-blk-ctl: Add ldb child node Laurentiu Palcu
2026-10-06 12:22   ` [PATCH v10 6/9] dt-bindings: clock: nxp, imx95-blk-ctl: " Laurentiu Palcu
2026-10-06 12:34   ` [PATCH v10 6/9] dt-bindings: clock: nxp,imx95-blk-ctl: " sashiko-bot
2026-10-07 13:11     ` Conor Dooley
2026-10-07 13:12   ` Conor Dooley
2026-10-07 13:57     ` Laurentiu Palcu
2026-10-07 14:02       ` Conor Dooley
2026-10-06 12:22 ` [PATCH v10 7/9] arm64: dts: imx94: Add display pipeline nodes Laurentiu Palcu
2026-10-06 12:22 ` [PATCH v10 8/9] arm64: dts: imx943-evk: Add display support using IT6263 Laurentiu Palcu
2026-10-06 12:22 ` [PATCH v10 9/9] MAINTAINERS: Add entry for i.MX94 DCIF driver Laurentiu Palcu

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=20261006123043.84A911F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=imx@lists.linux.dev \
    --cc=laurentiu.palcu@oss.nxp.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=robh@kernel.org \
    --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.