dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Jyri Sarha <jsarha@ti.com>
Cc: khilman@baylibre.com, dri-devel@lists.freedesktop.org,
	peter.ujfalusi@ti.com, bgolaszewski@baylibre.com,
	tomi.valkeinen@ti.com
Subject: Re: [PATCH v5 4/4] drm/tilcdc: Add drm bridge support for attaching drm bridge drivers
Date: Tue, 29 Nov 2016 22:27:37 +0200	[thread overview]
Message-ID: <1780152.QWRY83aPWY@avalon> (raw)
In-Reply-To: <daae8905-1288-2a84-8f0b-98184602546f@ti.com>

Hi Jyri,

On Tuesday 29 Nov 2016 22:18:56 Jyri Sarha wrote:
> On 11/25/16 11:02, Jyri Sarha wrote:
> > -void tilcdc_remove_external_encoders(struct drm_device *dev)
> > +void tilcdc_remove_external_device(struct drm_device *dev)
> >  {
> >  	struct tilcdc_drm_private *priv = dev->dev_private;
> > -	int i;
> > 
> >  	/* Restore the original helper functions, if any. */
> > -	for (i = 0; i < priv->num_connectors; i++)
> > -		if (IS_ERR(priv->connector_funcs[i]))
> > -			drm_connector_helper_add(priv->connectors[i], NULL);
> > -		else if (priv->connector_funcs[i])
> > -			drm_connector_helper_add(priv->connectors[i],
> > -						 priv->connector_funcs[i]);
> > +	if (IS_ERR(priv->connector_funcs))
> > +		drm_connector_helper_add(priv->external_connector, NULL);
> > +	else if (priv->connector_funcs)
> > +		drm_connector_helper_add(priv->external_connector,
> > +					 priv->connector_funcs);
> 
> I still need to add:
> +
> +       if (priv->external_encoder && priv->external_encoder->bridge)
> +               drm_bridge_detach(priv->external_encoder->bridge);

"drm: bridge: Detach bridge from encoder at encoder cleanup time" :-)

> > +}
> 
> ... and reorder the tilcdc_fini() a bit. I need to put
> tilcdc_remove_external_device() before drm_mode_config_cleanup()
> for drm_bridge_detach() to be called before whole mode config is teared
> apart.
> 
> There is also a bug in tearing down drm debugfs that had to be fixed
> before I got module unload and reload to work properly. I'll send a
> patch shortly.

-- 
Regards,

Laurent Pinchart

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-11-29 20:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-25  9:02 [PATCH v5 0/4] drm/tilcdc: Add bridge support and sync-lost flood recovery Jyri Sarha
2016-11-25  9:02 ` [PATCH v5 1/4] drm/tilcdc: Recover from sync lost error flood by resetting the LCDC Jyri Sarha
2016-11-25  9:02 ` [PATCH v5 2/4] dt-bindings: Move "ti, tfp410.txt" from display/ti to display/bridge Jyri Sarha
2016-11-25  9:02 ` [PATCH v5 3/4] drm/bridge: Add ti-tfp410 DVI transmitter driver Jyri Sarha
2016-11-29 20:18   ` Jyri Sarha
2016-11-29 20:26     ` Laurent Pinchart
2016-11-29 21:09       ` Jyri Sarha
2016-11-25  9:02 ` [PATCH v5 4/4] drm/tilcdc: Add drm bridge support for attaching drm bridge drivers Jyri Sarha
2016-11-29 20:18   ` Jyri Sarha
2016-11-29 20:27     ` Laurent Pinchart [this message]
2016-11-25 11:15 ` [PATCH v5 0/4] drm/tilcdc: Add bridge support and sync-lost flood recovery Bartosz Golaszewski

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=1780152.QWRY83aPWY@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jsarha@ti.com \
    --cc=khilman@baylibre.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=tomi.valkeinen@ti.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