All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luca Ceresoli" <luca.ceresoli@bootlin.com>
To: "Paul Cercueil" <paul@crapouillou.net>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	<linux-kernel@vger.kernel.org>
Cc: "H. Nikolaus Schaller" <hns@goldelico.com>,
	"Paul Boddie" <paul@boddie.org.uk>,
	"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>,
	"Luca Ceresoli" <luca.ceresoli@bootlin.com>,
	"open list:INGENIC JZ47xx SoCs" <linux-mips@vger.kernel.org>,
	"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/ingenic: Allocate and register the internal bridge separately
Date: Tue, 10 Nov 2026 15:39:57 +0100	[thread overview]
Message-ID: <DMRLX6IMODXH.1Q23T2VEIJVWI@bootlin.com> (raw)
In-Reply-To: <fb84cd36838875ccd2530b9e3983700fbd23eb3c.camel@crapouillou.net>

On Mon Nov 9, 2026 at 8:46 PM CET, Paul Cercueil wrote:
> Hi,
>
> Le jeudi 05 novembre 2026 à 12:35 -0800, Florian Fainelli a écrit :
>> The LCD controller's internal bridge is embedded in an object
>> allocated
>> with drmm_encoder_alloc(). This initializes the encoder but leaves
>> the
>> bridge's reference count at zero. Since drm_bridge_attach() takes a
>> reference, probing the CI20 display produces addition-on-zero and
>> underflow warnings and fails to attach the HDMI bridge chain.
>>
>> Allocate the internal bridge with devm_drm_bridge_alloc() and
>> register
>> it with devm_drm_bridge_add() before attaching it. Keep the encoder
>> in a
>> separate DRM-managed allocation: encoder cleanup can drop the final
>> bridge reference before it has finished accessing the encoder. Find
>> the internal bridge through the encoder's bridge chain during mode
>> setting, and use the bridge argument directly in bridge callbacks.
>>
>> Fixes: 94d50c1a2ca3 ("drm/bridge: get/put the bridge reference in
>> drm_bridge_attach/detach()")
>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>
> Looks like I lost my commit rights to drm-misc-next, I guess for
> inactivity.
>
> So I'll ack it (LGTM) and let someone else (Maxime?) commit it.

Ah, OK, I'll add it to my pipeline then.

> Reviewed-by: Paul Cercueil <paul@crapouillou.net>

Thanks!

Cheers,
Luca

--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2026-11-10 14:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05 20:35 [PATCH] drm/ingenic: Allocate and register the internal bridge separately Florian Fainelli
2026-11-06 10:59 ` H. Nikolaus Schaller
2026-11-06 12:21   ` Paul Cercueil
2026-11-06 12:28     ` H. Nikolaus Schaller
2026-11-06 13:51       ` Luca Ceresoli
2026-11-09 19:46 ` Paul Cercueil
2026-11-10 14:39   ` Luca Ceresoli [this message]
2026-11-10 14:45   ` Maxime Ripard
2026-11-10 17:05     ` Paul Cercueil

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=DMRLX6IMODXH.1Q23T2VEIJVWI@bootlin.com \
    --to=luca.ceresoli@bootlin.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=f.fainelli@gmail.com \
    --cc=hns@goldelico.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=paul@boddie.org.uk \
    --cc=paul@crapouillou.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.