From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Ravi, Deepthy" <deepthy.ravi@ti.com>
Cc: "mchehab@infradead.org" <mchehab@infradead.org>,
"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>,
"Hiremath, Vaibhav" <hvaibhav@ti.com>
Subject: Re: [PATCHv2] ISP:BUILD:FIX: Move media_entity_init() and
Date: Wed, 24 Aug 2011 13:29:47 +0200 [thread overview]
Message-ID: <201108241329.48147.laurent.pinchart@ideasonboard.com> (raw)
In-Reply-To: <ADF30F4D7BDE934D9B632CE7D5C7ACA4047C4D0907F6@dbde03.ent.ti.com>
Hi,
On Wednesday 24 August 2011 13:21:27 Ravi, Deepthy wrote:
> On Wed, Aug 24, 2011 at 4:47 PM, Laurent Pinchart wrote:
> > On Friday 19 August 2011 15:48:45 Deepthy Ravi wrote:
> >> From: Vaibhav Hiremath <hvaibhav@ti.com>
> >>
> >> Fix the build break caused when CONFIG_MEDIA_CONTROLLER
> >> option is disabled and if any sensor driver has to be used
> >> between MC and non MC framework compatible devices.
> >>
> >> For example,if tvp514x video decoder driver migrated to
> >> MC framework is being built without CONFIG_MEDIA_CONTROLLER
> >> option enabled, the following error messages will result.
> >> drivers/built-in.o: In function `tvp514x_remove':
> >> drivers/media/video/tvp514x.c:1285: undefined reference to
> >> `media_entity_cleanup'
> >> drivers/built-in.o: In function `tvp514x_probe':
> >> drivers/media/video/tvp514x.c:1237: undefined reference to
> >> `media_entity_init'
> >
> > If the tvp514x is migrated to the MC framework, its Kconfig option should
> > depend on MEDIA_CONTROLLER.
>
> The same TVP514x driver is being used for both MC and non MC compatible
> devices, for example OMAP3 and AM35x. So if it is made dependent on MEDIA
> CONTROLLER, we cannot enable the driver for MC independent devices.
Then you should use conditional compilation in the tvp514x driver itself. Or
better, port the AM35x driver to the MC API.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2011-08-24 11:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 13:48 Deepthy Ravi
2011-08-24 10:17 ` Laurent Pinchart
2011-08-24 11:21 ` Ravi, Deepthy
2011-08-24 11:29 ` Laurent Pinchart [this message]
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
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=201108241329.48147.laurent.pinchart@ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=deepthy.ravi@ti.com \
--cc=hvaibhav@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mchehab@infradead.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
all inboxes | Powered by JetHome®