dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	airlied@gmail.com, simona@ffwll.ch, lumag@kernel.org,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] drm/connector: check if destroy function exist
Date: Tue, 28 Jul 2026 20:36:09 +0200	[thread overview]
Message-ID: <amj2mUdABXd3XW9G@akepd> (raw)
In-Reply-To: <44557a30-dc86-409a-b430-2b4db151843b@suse.de>

On Fri, Jul 03, 2026 at 09:09:46AM +0200, Thomas Zimmermann wrote:
> Hi
> 
> Am 02.07.26 um 21:14 schrieb Andreas Kemnade:
> > Connectors might have not resources needed to be manually freed.
> > E.g. the drm_bridge_connector does not have such a callback.
> > 
> > Fixes: c12907be57b1 ("drm/bridge-connector: switch to using drmm allocations")
> 
> This patch uses drmm_connector_init() for the cleanup, which is a mis-design
> IMHO.  Rather than calling drm_connector_cleanup(), it should call
> connector->funcs->destroy, which then points to drm_connector_cleanup. This
> would make the whole thing more useful and not require fixups (like this
> one) elsewhere in the code. Just just my 2cts.
> 
That just sounds like a revert to me. But maybe I misunterstand your comment
> Best regards
> Thomas
> 
> 
> > Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
> > ---
> >   drivers/gpu/drm/drm_connector.c | 8 ++++++--
> >   1 file changed, 6 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/drm_connector.c b/drivers/gpu/drm/drm_connector.c
> > index 47dc53c4a738..d2dfc6e8f7d0 100644
> > --- a/drivers/gpu/drm/drm_connector.c
> > +++ b/drivers/gpu/drm/drm_connector.c
> > @@ -198,7 +198,9 @@ static void drm_connector_free(struct kref *kref)
> >   	struct drm_device *dev = connector->dev;
> >   	drm_mode_object_unregister(dev, &connector->base);
> > -	connector->funcs->destroy(connector);
> > +
> > +	if (connector->funcs->destroy)
> > +		connector->funcs->destroy(connector);
> >   }
> >   void drm_connector_free_work_fn(struct work_struct *work)
> > @@ -216,7 +218,9 @@ void drm_connector_free_work_fn(struct work_struct *work)
> >   	llist_for_each_entry_safe(connector, n, freed, free_node) {
> >   		drm_mode_object_unregister(dev, &connector->base);
> > -		connector->funcs->destroy(connector);
> > +
> > +		if (connector->funcs->destroy)
> > +			connector->funcs->destroy(connector);
> >   	}
> >   }
> 
> -- 
> --
> Thomas Zimmermann
> Graphics Driver Developer
> SUSE Software Solutions Germany GmbH
> Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
> GF: Jochen Jaser, Andrew McDonald, Werner Knoblich, (HRB 36809, AG Nürnberg)
> 
> 
> 

      reply	other threads:[~2026-07-29  7:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 19:14 [PATCH RESEND] drm/connector: check if destroy function exist Andreas Kemnade
2026-07-02 19:36 ` sashiko-bot
2026-07-03  7:09 ` Thomas Zimmermann
2026-07-28 18:36   ` Andreas Kemnade [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=amj2mUdABXd3XW9G@akepd \
    --to=andreas@kemnade.info \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lumag@kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    /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