From: Maxime Ripard <mripard@kernel.org>
To: Liu Ying <victor.liu@nxp.com>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
andrzej.hajda@intel.com, neil.armstrong@linaro.org,
rfoss@kernel.org, Laurent.pinchart@ideasonboard.com,
jonas@kwiboo.se, jernej.skrabec@gmail.com,
maarten.lankhorst@linux.intel.com, tzimmermann@suse.de,
airlied@gmail.com, simona@ffwll.ch
Subject: Re: [PATCH 5/5] drm/bridge: simple-bridge: Add next panel support
Date: Tue, 4 Mar 2025 11:41:44 +0100 [thread overview]
Message-ID: <20250304-interesting-solemn-potoo-fd4c6e@houat> (raw)
In-Reply-To: <20250304101530.969920-6-victor.liu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 3653 bytes --]
On Tue, Mar 04, 2025 at 06:15:30PM +0800, Liu Ying wrote:
> The next bridge connected to a simple bridge could be a panel, e.g.,
> a DPI panel connected to a DPI color encoder. Add the next panel support,
> instead of supporting non-panel next bridge only.
>
> Signed-off-by: Liu Ying <victor.liu@nxp.com>
> ---
> drivers/gpu/drm/bridge/Kconfig | 1 +
> drivers/gpu/drm/bridge/simple-bridge.c | 32 ++++++++++++++++----------
> 2 files changed, 21 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/gpu/drm/bridge/Kconfig b/drivers/gpu/drm/bridge/Kconfig
> index d20f1646dac2..92187dbdd32b 100644
> --- a/drivers/gpu/drm/bridge/Kconfig
> +++ b/drivers/gpu/drm/bridge/Kconfig
> @@ -310,6 +310,7 @@ config DRM_SIMPLE_BRIDGE
> tristate "Simple DRM bridge support"
> depends on OF
> select DRM_KMS_HELPER
> + select DRM_PANEL_BRIDGE
> help
> Support for non-programmable DRM bridges, such as ADI ADV7123, TI
> THS8134 and THS8135 or passive resistor ladder DACs.
> diff --git a/drivers/gpu/drm/bridge/simple-bridge.c b/drivers/gpu/drm/bridge/simple-bridge.c
> index c0445bd20e07..4c585e5583ca 100644
> --- a/drivers/gpu/drm/bridge/simple-bridge.c
> +++ b/drivers/gpu/drm/bridge/simple-bridge.c
> @@ -19,6 +19,7 @@
> #include <drm/drm_crtc.h>
> #include <drm/drm_edid.h>
> #include <drm/drm_of.h>
> +#include <drm/drm_panel.h>
> #include <drm/drm_print.h>
> #include <drm/drm_probe_helper.h>
>
> @@ -35,6 +36,7 @@ struct simple_bridge {
> const struct simple_bridge_info *info;
>
> struct drm_bridge *next_bridge;
> + struct drm_panel *next_panel;
> struct regulator *vdd;
> struct gpio_desc *enable;
>
> @@ -114,6 +116,10 @@ static int simple_bridge_attach(struct drm_bridge *bridge,
> struct simple_bridge *sbridge = drm_bridge_to_simple_bridge(bridge);
> int ret;
>
> + if (sbridge->next_panel)
> + return drm_bridge_attach(bridge->encoder, sbridge->next_bridge,
> + bridge, flags);
> +
> ret = drm_bridge_attach(bridge->encoder, sbridge->next_bridge, bridge,
> DRM_BRIDGE_ATTACH_NO_CONNECTOR);
> if (ret < 0)
> @@ -247,7 +253,6 @@ static int simple_bridge_get_dpi_color_coding(struct simple_bridge *sbridge,
> static int simple_bridge_probe(struct platform_device *pdev)
> {
> struct simple_bridge *sbridge;
> - struct device_node *remote;
> int ret;
>
> sbridge = devm_kzalloc(&pdev->dev, sizeof(*sbridge), GFP_KERNEL);
> @@ -257,17 +262,20 @@ static int simple_bridge_probe(struct platform_device *pdev)
> sbridge->info = of_device_get_match_data(&pdev->dev);
>
> /* Get the next bridge in the pipeline. */
> - remote = of_graph_get_remote_node(pdev->dev.of_node, 1, -1);
> - if (!remote)
> - return -EINVAL;
> -
> - sbridge->next_bridge = of_drm_find_bridge(remote);
> - of_node_put(remote);
> -
> - if (!sbridge->next_bridge) {
> - dev_dbg(&pdev->dev, "Next bridge not found, deferring probe\n");
> - return -EPROBE_DEFER;
> - }
> + ret = drm_of_find_panel_or_bridge(pdev->dev.of_node, 1, -1,
> + &sbridge->next_panel,
> + &sbridge->next_bridge);
> + if (ret)
> + return dev_err_probe(&pdev->dev, ret,
> + "Next panel or bridge not found\n");
> +
> + if (sbridge->next_panel)
> + sbridge->next_bridge = devm_drm_panel_bridge_add(&pdev->dev,
> + sbridge->next_panel);
> +
> + if (IS_ERR(sbridge->next_bridge))
> + return dev_err_probe(&pdev->dev, PTR_ERR(sbridge->next_bridge),
> + "Next bridge not found\n");
This makes sense in general, but I think a better approach would be to
use devm/drmm_of_get_bridge here.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
next prev parent reply other threads:[~2025-03-04 10:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 10:15 [PATCH 0/5] drm/bridge: simple-bridge: Add DPI color encoder support Liu Ying
2025-03-04 10:15 ` [PATCH 1/5] dt-bindings: display: Document DPI color codings Liu Ying
2025-03-04 10:33 ` Maxime Ripard
2025-03-05 7:51 ` Krzysztof Kozlowski
2025-03-05 8:26 ` Maxime Ripard
2025-03-05 12:16 ` Krzysztof Kozlowski
2025-03-06 7:13 ` Liu Ying
2025-03-04 10:15 ` [PATCH 2/5] drm/of: Add drm_of_dpi_get_color_coding() Liu Ying
2025-03-04 10:15 ` [PATCH 3/5] dt-bindings: display: simple-bridge: Document DPI color encoder Liu Ying
2025-03-04 10:38 ` Maxime Ripard
2025-03-06 5:49 ` Liu Ying
2025-03-04 11:27 ` Rob Herring (Arm)
2025-03-04 15:23 ` Rob Herring
2025-03-05 9:35 ` Alexander Stein
2025-03-05 16:38 ` Rob Herring
2025-03-06 7:02 ` Liu Ying
2025-03-06 11:35 ` Maxime Ripard
2025-03-06 20:34 ` Rob Herring
2025-03-07 3:25 ` Liu Ying
2025-03-10 9:53 ` Maxime Ripard
2025-03-11 2:29 ` Liu Ying
2025-03-11 7:44 ` Maxime Ripard
2025-03-07 3:10 ` Liu Ying
2025-03-10 9:44 ` Maxime Ripard
2025-03-11 2:38 ` Liu Ying
2025-03-11 7:52 ` Maxime Ripard
2025-03-04 10:15 ` [PATCH 4/5] drm/bridge: simple-bridge: Add DPI color encoder support Liu Ying
2025-03-04 10:40 ` Maxime Ripard
2025-03-06 5:57 ` Liu Ying
2025-03-04 10:15 ` [PATCH 5/5] drm/bridge: simple-bridge: Add next panel support Liu Ying
2025-03-04 10:41 ` Maxime Ripard [this message]
2025-03-06 6:17 ` Liu Ying
2025-03-04 15:00 ` [PATCH 0/5] drm/bridge: simple-bridge: Add DPI color encoder support Alexander Stein
2026-01-12 9:31 ` Francesco Dolcini
2026-01-12 9:44 ` Liu Ying
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=20250304-interesting-solemn-potoo-fd4c6e@houat \
--to=mripard@kernel.org \
--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@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=victor.liu@nxp.com \
/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