From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
kyungmin.park@samsung.com, a.hajda@samsung.com
Subject: Re: [RFC PATCH v3 0/2] Media entity links handling
Date: Tue, 11 Jun 2013 13:36:46 +0200 [thread overview]
Message-ID: <51B70BCE.6010709@samsung.com> (raw)
In-Reply-To: <20130611105032.GJ3103@valkosipuli.retiisi.org.uk>
Hi Sakari,
On 06/11/2013 12:50 PM, Sakari Ailus wrote:
> On Mon, Jun 10, 2013 at 04:54:28PM +0200, Sylwester Nawrocki wrote:
>> This is an updated version of the patch set
>> http://www.spinics.net/lists/linux-media/msg64536.html
>>
>> Comparing to v2 it includes improvements of the __media_entity_remove_links()
>> function, thanks to Sakari.
>>
>> The cover letter of v2 is included below.
>>
>> This small patch set adds a function for removing all links at a media
>> entity. I found out such a function is needed when media entites that
>> belong to a single media device have drivers in different kernel modules.
>> This means virtually all camera drivers, since sensors are separate
>> modules from the host interface drivers.
>>
>> More details can be found at each patch's description.
>>
>> The links removal from a media entity is rather strightforward, but when
>> and where links should be created/removed is not immediately clear to me.
>>
>> I assumed that links should normally be created/removed when an entity
>> is registered to its media device, with the graph mutex held.
>>
>> I'm open to opinions whether it's good or not and possibly suggestions
>> on how those issues could be handled differently.
>>
>> The changes since original version are listed in patch 1/2, in patch 2/2
>> only the commit description has changed slightly.
>
> Acked-by: Sakari Ailus <sakari.ailus@iki.fi>
>
> That said, I'd wish they won't be merged before the two patches I'm sending
> shortly. The thing is that the media entity links array is freed by
> media_entity_cleanup(), and there are two drivers that call
> media_entity_cleanup() first. The patches fix the issue, so could you
> prepend them to your set (after review, naturally)?
Your patches look good, thanks a lot for inspecting those drivers! I'm going
to put all those patches on a separate branch and will hold on with sending
a pull request for a couple days.
Regards,
Sylwester
next prev parent reply other threads:[~2013-06-11 11:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 14:54 [RFC PATCH v3 0/2] Media entity links handling Sylwester Nawrocki
2013-06-10 14:54 ` Sylwester Nawrocki
2013-06-11 10:50 ` Sakari Ailus
2013-06-11 10:50 ` [RFC PATCH 1/2] smiapp: Clean up media entity after unregistering subdev Sakari Ailus
2013-06-11 10:50 ` [RFC PATCH 2/2] davinci_vpfe: " Sakari Ailus
2013-06-11 11:38 ` Sylwester Nawrocki
2013-06-12 4:44 ` Prabhakar Lad
2013-06-16 21:16 ` Sylwester Nawrocki
2013-06-17 8:07 ` Prabhakar Lad
2013-06-17 20:43 ` Sakari Ailus
2013-06-11 11:38 ` [RFC PATCH 1/2] smiapp: " Sylwester Nawrocki
2013-06-11 11:36 ` Sylwester Nawrocki [this message]
2013-06-10 14:54 ` [RFC PATCH v3 1/2] media: Add a function removing all links of a media entity Sylwester Nawrocki
2013-06-11 11:44 ` Sylwester Nawrocki
2013-06-10 14:54 ` [RFC PATCH v3 2/2] V4L: Remove all links of a media entity when unregistering subdev Sylwester Nawrocki
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=51B70BCE.6010709@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=a.hajda@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
/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.