All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Javier Martinez Canillas <javier@osg.samsung.com>,
	Shuah Khan <shuahkh@osg.samsung.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Greg KH <greg@kroah.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: Re: [PATCH RFC] omap3isp: prevent releasing MC too early
Date: Fri, 16 Dec 2016 09:18:50 -0200	[thread overview]
Message-ID: <20161216091850.688dd863@vento.lan> (raw)
In-Reply-To: <2965200.xcWXyJedNO@avalon>


Em Thu, 15 Dec 2016 16:04:51 +0200
Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:

We have now two threads discussing the same subject, which is bad, as
we'll end repeating the same arguments on different threads...

Let's use the "[PATCH RFC 00/21]" for those discussions, as it seems we're
reaching to somewhere there.

> Even if you're not entirely convinced by the reasons 
> explained in this mail thread, remember that we will need sooner or later to 
> implement support for media graph update at runtime. Refcounting will be 
> needed, let's design it in the cleanest possible way.

As I said, I'm not against using some other approach and even
adding refcounting to each graph object.

What I am against is on a patchset that starts by breaking 
the USB drivers that use the media controller.

Btw, I'm starting to suspect that getting rid of devm_*alloc()
on OMAP3, as proposed by the 00/21 thread is addressing a symptom of
the problem and not a cause, and that using get_device()/put_device()
may help fixing such issues. See Hans comments on that thread.

Thanks,
Mauro

  reply	other threads:[~2016-12-16 11:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14 15:14 [PATCH RFC] omap3isp: prevent releasing MC too early Mauro Carvalho Chehab
2016-12-15 12:13 ` Laurent Pinchart
2016-12-15 12:31   ` Greg KH
2016-12-15 15:07     ` Laurent Pinchart
2016-12-15 16:58     ` Mauro Carvalho Chehab
2016-12-15 12:37   ` Mauro Carvalho Chehab
2016-12-15 12:42     ` Javier Martinez Canillas
2016-12-15 12:57       ` Mauro Carvalho Chehab
2016-12-15 13:44         ` Greg KH
2016-12-15 14:17           ` Mauro Carvalho Chehab
2016-12-16  8:21             ` Sakari Ailus
2016-12-16 11:44               ` Sakari Ailus
2016-12-15 14:04         ` Laurent Pinchart
2016-12-16 11:18           ` Mauro Carvalho Chehab [this message]
2016-12-16 16:06             ` Laurent Pinchart
2016-12-15 13:24     ` 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=20161216091850.688dd863@vento.lan \
    --to=mchehab@s-opensource.com \
    --cc=greg@kroah.com \
    --cc=javier@osg.samsung.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=shuahkh@osg.samsung.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.