public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: Amin GATTOUT <amin.gattout@gmail.com>,
	Tomi Valkeinen <tomi.valkeinen+renesas@ideasonboard.com>,
	Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	dri-devel@lists.freedesktop.org,
	linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/rcar-du: Convert to of_drm_find_and_get_bridge()
Date: Fri, 27 Mar 2026 10:34:04 +0200	[thread overview]
Message-ID: <20260327083404.GA2993961@killaraus.ideasonboard.com> (raw)
In-Reply-To: <DHDEL0VTRYDP.2D45EP8E07Y08@bootlin.com>

Hi Luca,

On Fri, Mar 27, 2026 at 08:57:45AM +0100, Luca Ceresoli wrote:
> On Thu Mar 26, 2026 at 9:10 PM CET, Amin GATTOUT wrote:
> > of_drm_find_bridge() is deprecated.
> > Replace it with of_drm_find_and_get_bridge() which increments
> > the bridge refcount as required.
> 
> Thanks for taking care of the conversion to the new API!

I suspect you may be talking to a machine (possibly through a human
proxy).

> > --- a/drivers/gpu/drm/renesas/rcar-du/rcar_du_encoder.c
> > +++ b/drivers/gpu/drm/renesas/rcar-du/rcar_du_encoder.c
> > @@ -72,7 +72,7 @@ int rcar_du_encoder_init(struct rcar_du_device *rcdu,
> >  		if (IS_ERR(bridge))
> >  			return PTR_ERR(bridge);
> >  	} else {
> > -		bridge = of_drm_find_bridge(enc_node);
> > +		bridge = of_drm_find_and_get_bridge(enc_node);
> 
> This change alone is not correct I'm afraid. The difference between
> of_drm_find_bridge() and of_drm_find_and_get_bridge() is the latter get a
> reference to the bridge, so you have to put that reference when the bridge
> pointer is no more accessible.
> 
> Have a look at previous commits doing the same API replacement, you can
> find examples similar to this one, where:
> 
>  * the bridge pointer is stored in a local variable (not saved in a struct)
>  * the bridge pointer could be set wither by of_drm_find_bridge() or
>    a function adding a panel bridge
> 
> Luca

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2026-03-27  8:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 20:10 [PATCH] drm/rcar-du: Convert to of_drm_find_and_get_bridge() Amin GATTOUT
2026-03-26 20:24 ` Laurent Pinchart
2026-03-27  7:57 ` Luca Ceresoli
2026-03-27  8:34   ` Laurent Pinchart [this message]
2026-03-27  8:54     ` Amin
2026-03-27  9:04       ` Laurent Pinchart

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=20260327083404.GA2993961@killaraus.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=amin.gattout@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert+renesas@glider.be \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=luca.ceresoli@bootlin.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=magnus.damm@gmail.com \
    --cc=mripard@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tomi.valkeinen+renesas@ideasonboard.com \
    --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