All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Eric Anholt <eric@anholt.net>
Cc: dri-devel@lists.freedesktop.org,
	Archit Taneja <architt@codeaurora.org>,
	Andrzej Hajda <a.hajda@samsung.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-kernel@vger.kernel.org,
	Daniel Vetter <daniel.vetter@ffwl.ch>
Subject: Re: [PATCH v5 2/6] drm/bridge: Add a devm_ allocator for panel bridge.
Date: Sat, 05 Aug 2017 00:25:08 +0300	[thread overview]
Message-ID: <1610977.GUN5zSZ7yI@avalon> (raw)
In-Reply-To: <87zibfqd1u.fsf@eliezer.anholt.net>

Hi Eric,

On Friday 04 Aug 2017 13:43:25 Eric Anholt wrote:
> Laurent Pinchart <laurent.pinchart@ideasonboard.com> writes:
> > On Tuesday 18 Jul 2017 14:05:06 Eric Anholt wrote:
> >> This will let drivers reduce the error cleanup they need, in
> >> particular the "is_panel_bridge" flag.
> >> 
> >> v2: Slight cleanup of remove function by Andrzej
> > 
> > I just want to point out that, in the context of Daniel's work on
> > hot-unplug, 90% of the devm_* allocations are wrong and will get in the
> > way. All DRM core objects that are accessible one way or another from
> > userspace will need to be properly reference-counted and freed only when
> > the last reference disappears, which could be well after the
> > corresponding device is removed. I believe this could be one such objects
> > :-/
> 
> Sure, if you're hotplugging, your life is pain.  For non-hotpluggable
> devices, like our SOC platform devices (current panel-bridge consumers),
> this still seems like an excellent simplification of memory management.

It encourages driver writers to write code that they will have to fix later. 
That's certainly a simplification, but certainly not a good thing in my 
opinion :-)

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2017-08-04 21:25 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 21:05 [PATCH v5 1/6] drm/vc4: Avoid using vrefresh==0 mode in DSI htotal math Eric Anholt
2017-07-18 21:05 ` Eric Anholt
2017-07-18 21:05 ` [PATCH v5 2/6] drm/bridge: Add a devm_ allocator for panel bridge Eric Anholt
2017-07-18 21:05   ` Eric Anholt
2017-07-19  8:58   ` Philippe CORNU
2017-07-19  8:58     ` Philippe CORNU
2017-07-26 22:43     ` Eric Anholt
2017-07-26 22:43       ` Eric Anholt
2017-08-04 13:46   ` Laurent Pinchart
2017-08-04 14:57     ` Laurent Pinchart
2017-08-04 20:43     ` Eric Anholt
2017-08-04 21:25       ` Laurent Pinchart [this message]
2017-08-04 22:19       ` Ilia Mirkin
2017-08-04 22:19         ` Ilia Mirkin
2017-08-05 10:59         ` Noralf Trønnes
2017-08-05 10:59           ` Noralf Trønnes
2017-08-05 14:47           ` Noralf Trønnes
2017-08-07  9:25           ` Daniel Vetter
2017-08-07  9:25             ` Daniel Vetter
2017-08-07 10:22             ` Laurent Pinchart
2017-08-07 10:22               ` Laurent Pinchart
2017-08-07 14:37               ` Noralf Trønnes
2017-08-07 14:59               ` Daniel Vetter
2017-08-07 14:59                 ` Daniel Vetter
2017-08-07 21:54                 ` Laurent Pinchart
2017-08-07 21:54                   ` Laurent Pinchart
2017-07-18 21:05 ` [PATCH v5 3/6] drm/vc4: Delay DSI host registration until the panel has probed Eric Anholt
2017-07-18 21:05   ` Eric Anholt
2017-08-04  9:04   ` Boris Brezillon
2017-07-18 21:05 ` [PATCH v5 4/6] drm: Allow DSI devices to be registered before the host registers Eric Anholt
2017-07-18 21:05   ` Eric Anholt
2017-07-19 20:31   ` Eric Anholt
2017-07-19 20:31     ` Eric Anholt
2017-07-18 21:05 ` [PATCH v5 5/6] dt-bindings: Document the Raspberry Pi Touchscreen nodes Eric Anholt
2017-07-18 21:05   ` Eric Anholt
2017-07-18 21:05 ` [PATCH v5 6/6] drm/panel: Add support for the Raspberry Pi 7" Touchscreen Eric Anholt
2017-07-18 21:05   ` Eric Anholt
2017-08-04  8:53 ` [PATCH v5 1/6] drm/vc4: Avoid using vrefresh==0 mode in DSI htotal math Boris Brezillon
2017-08-04 21:15   ` Eric Anholt
2017-08-04 21:15     ` Eric Anholt
2017-08-09 14:42     ` Boris Brezillon
2017-08-09 14:42       ` Boris Brezillon

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=1610977.GUN5zSZ7yI@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=a.hajda@samsung.com \
    --cc=architt@codeaurora.org \
    --cc=daniel.vetter@ffwl.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eric@anholt.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thierry.reding@gmail.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 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.