public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Liu Ying <victor.liu@nxp.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	mripard@kernel.org, neil.armstrong@linaro.org,
	ulf.hansson@linaro.org, rfoss@kernel.org, tzimmermann@suse.de,
	jonas@kwiboo.se, jernej.skrabec@gmail.com,
	Laurent.pinchart@ideasonboard.com, andrzej.hajda@intel.com,
	angelogioacchino.delregno@collabora.com,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] drm/bridge: panel: Check device dependency before managing device link
Date: Mon, 27 Nov 2023 15:35:38 +0200	[thread overview]
Message-ID: <ZWSbKkgs8V4sdy8T@intel.com> (raw)
In-Reply-To: <20231123032615.3760488-1-victor.liu@nxp.com>

On Thu, Nov 23, 2023 at 11:26:15AM +0800, Liu Ying wrote:
> Some panel devices already depend on DRM device, like the panel in
> arch/arm/boot/dts/st/ste-ux500-samsung-skomer.dts, because DRM device is
> the ancestor of those panel devices.  device_link_add() would fail by
> returning a NULL pointer for those panel devices because of the existing
> dependency.  So, check the dependency by calling device_is_dependent()
> before adding or deleting device link between panel device and DRM device
> so that the link is managed only for independent panel devices.
> 
> Fixes: 887878014534 ("drm/bridge: panel: Fix device link for DRM_BRIDGE_ATTACH_NO_CONNECTOR")
> Fixes: 199cf07ebd2b ("drm/bridge: panel: Add a device link between drm device and panel device")
> Reported-by: Linus Walleij <linus.walleij@linaro.org>
> Closes: https://lore.kernel.org/lkml/CACRpkdaGzXD6HbiX7mVUNJAJtMEPG00Pp6+nJ1P0JrfJ-ArMvQ@mail.gmail.com/T/
> Tested-by: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Liu Ying <victor.liu@nxp.com>
> ---
>  drivers/gpu/drm/bridge/panel.c | 27 ++++++++++++++++++---------
>  1 file changed, 18 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/gpu/drm/bridge/panel.c b/drivers/gpu/drm/bridge/panel.c
> index e48823a4f1ed..5e8980023407 100644
> --- a/drivers/gpu/drm/bridge/panel.c
> +++ b/drivers/gpu/drm/bridge/panel.c
> @@ -23,6 +23,7 @@ struct panel_bridge {
>  	struct drm_panel *panel;
>  	struct device_link *link;
>  	u32 connector_type;
> +	bool is_independent;
>  };
>  
>  static inline struct panel_bridge *
> @@ -67,12 +68,17 @@ static int panel_bridge_attach(struct drm_bridge *bridge,
>  	struct drm_device *drm_dev = bridge->dev;
>  	int ret;
>  
> -	panel_bridge->link = device_link_add(drm_dev->dev, panel->dev,
> -					     DL_FLAG_STATELESS);
> -	if (!panel_bridge->link) {
> -		DRM_ERROR("Failed to add device link between %s and %s\n",
> -			  dev_name(drm_dev->dev), dev_name(panel->dev));
> -		return -EINVAL;
> +	panel_bridge->is_independent = !device_is_dependent(drm_dev->dev,
> +							    panel->dev);

This broke the build. Looks like device_is_dependent() is not even exported.
ERROR: modpost: "device_is_dependent" [drivers/gpu/drm/drm_kms_helper.ko] undefined!

The recommended defconfigs in rerere-cache do seem to have CONFIG_DRM_KMS_HELPER=m
so this should have been caught before pushing. How did it slip through?

> +
> +	if (panel_bridge->is_independent) {
> +		panel_bridge->link = device_link_add(drm_dev->dev, panel->dev,
> +						     DL_FLAG_STATELESS);
> +		if (!panel_bridge->link) {
> +			DRM_ERROR("Failed to add device link between %s and %s\n",
> +				  dev_name(drm_dev->dev), dev_name(panel->dev));
> +			return -EINVAL;
> +		}
>  	}
>  
>  	if (flags & DRM_BRIDGE_ATTACH_NO_CONNECTOR)
> @@ -80,7 +86,8 @@ static int panel_bridge_attach(struct drm_bridge *bridge,
>  
>  	if (!bridge->encoder) {
>  		DRM_ERROR("Missing encoder\n");
> -		device_link_del(panel_bridge->link);
> +		if (panel_bridge->is_independent)
> +			device_link_del(panel_bridge->link);
>  		return -ENODEV;
>  	}
>  
> @@ -92,7 +99,8 @@ static int panel_bridge_attach(struct drm_bridge *bridge,
>  				 panel_bridge->connector_type);
>  	if (ret) {
>  		DRM_ERROR("Failed to initialize connector\n");
> -		device_link_del(panel_bridge->link);
> +		if (panel_bridge->is_independent)
> +			device_link_del(panel_bridge->link);
>  		return ret;
>  	}
>  
> @@ -115,7 +123,8 @@ static void panel_bridge_detach(struct drm_bridge *bridge)
>  	struct panel_bridge *panel_bridge = drm_bridge_to_panel_bridge(bridge);
>  	struct drm_connector *connector = &panel_bridge->connector;
>  
> -	device_link_del(panel_bridge->link);
> +	if (panel_bridge->is_independent)
> +		device_link_del(panel_bridge->link);
>  
>  	/*
>  	 * Cleanup the connector if we know it was initialized.
> -- 
> 2.37.1

-- 
Ville Syrjälä
Intel

  parent reply	other threads:[~2023-11-27 13:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23  3:26 [PATCH] drm/bridge: panel: Check device dependency before managing device link Liu Ying
2023-11-24 23:48 ` Linus Walleij
2023-11-27 13:35 ` Ville Syrjälä [this message]
2023-11-27 16:08   ` Linus Walleij

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=ZWSbKkgs8V4sdy8T@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=andrzej.hajda@intel.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=rfoss@kernel.org \
    --cc=tzimmermann@suse.de \
    --cc=ulf.hansson@linaro.org \
    --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