From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: "Hiremath, Vaibhav" <hvaibhav@ti.com>,
"Ravi, Deepthy" <deepthy.ravi@ti.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCHv2] ISP:BUILD:FIX: Move media_entity_init() and
Date: Tue, 06 Sep 2011 23:50:54 -0300 [thread overview]
Message-ID: <4E66DC0E.4070006@infradead.org> (raw)
In-Reply-To: <201109061647.31861.laurent.pinchart@ideasonboard.com>
Em 06-09-2011 11:47, Laurent Pinchart escreveu:
> Hi Vaibhav,
>
> On Tuesday 06 September 2011 16:12:35 Hiremath, Vaibhav wrote:
>> On Monday, September 05, 2011 6:20 PM Laurent Pinchart wrote:
>>> On Sunday 04 September 2011 15:32:28 Mauro Carvalho Chehab wrote:
>>
>> <snip>
>>
>>> I don't mind splitting the config option. An alternative would be to
>>> compile media_entity_init() and media_entity_cleanup() based on
>>> CONFIG_MEDIA_SUPPORT instead of CONFIG_MEDIA_CONTROLLER, but that looks a
>>> bit hackish to me.
>>>
>>>> Also, I don't like the idea of increasing drivers complexity for the
>>>> existing drivers that work properly without MC. All those core
>>>> conversions that were done in the last two years caused already too much
>>>> instability to them.
>>>>
>>>> We should really avoid touching on them again for something that won't
>>>> be adding any new feature nor fixing any known bug.
>>>
>>> We don't have to convert them all in one go right now, we can implement
>>> pad-level operations support selectively when a subdev driver becomes used
>>> by an MC-enabled host/bridge driver.
>>
>> I completely agree that we should not be duplicating the code just for sake
>> of it.
>>
>> Isn't the wrapper approach seems feasible here?
>
> As explained in a previous e-mail, a wrapper sounds like a good approach to
> me, to emulate video::* operations based on pad::* operations. We want to move
> to pad::* operations, so we should not perform emulation the other way around.
We have 300+ drivers under /drivers/media. Just a few of them need MC API.
Good sense says that we shouldn't touch on 300+ just because of half dozen drivers.
So, if a wrapper is needed, it should be done for the other side.
Mauro.
prev parent reply other threads:[~2011-09-07 2:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 13:48 [PATCHv2] ISP:BUILD:FIX: Move media_entity_init() and Deepthy Ravi
2011-08-24 10:17 ` Laurent Pinchart
2011-08-24 11:21 ` Ravi, Deepthy
2011-08-24 11:29 ` Laurent Pinchart
2011-08-24 12:19 ` Hiremath, Vaibhav
2011-08-24 12:55 ` Andy Shevchenko
2011-08-24 13:19 ` Hiremath, Vaibhav
2011-08-24 13:25 ` Laurent Pinchart
2011-08-24 14:26 ` Hiremath, Vaibhav
2011-09-03 22:21 ` Mauro Carvalho Chehab
2011-09-04 9:01 ` Laurent Pinchart
2011-09-04 13:32 ` Mauro Carvalho Chehab
2011-09-05 12:49 ` Laurent Pinchart
2011-09-06 14:12 ` Hiremath, Vaibhav
2011-09-06 14:47 ` Laurent Pinchart
2011-09-07 2:50 ` Mauro Carvalho Chehab [this message]
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=4E66DC0E.4070006@infradead.org \
--to=mchehab@infradead.org \
--cc=deepthy.ravi@ti.com \
--cc=hvaibhav@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).