From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Kassey Lee <kassey1216@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-media@vger.kernel.org, g.liakhovetski@gmx.de,
Kassey Lee <ygli@marvell.com>, Daniel Drake <dsd@laptop.org>,
ytang5@marvell.com, qingx@marvell.com, leiwen@marvell.com
Subject: Re: [PATCH 1/8] marvell-cam: Move cafe-ccic into its own directory
Date: Wed, 15 Jun 2011 08:37:30 -0300 [thread overview]
Message-ID: <4DF8997A.8090007@infradead.org> (raw)
In-Reply-To: <BANLkTikmvsgBTLgu46xXYiUHmOVvGoZAag@mail.gmail.com>
Em 14-06-2011 23:01, Kassey Lee escreveu:
> Jon,
> if you agree to change it in another patch, and now just to keep
> it with the driver that works for years.
> that is OK. thanks.
> I am looking forward your patch based on VB2, because based on
> current cafe_ccic.c, it is hard to share with my driver.
>
> 2011/6/14 Jonathan Corbet <corbet@lwn.net>:
>> On Tue, 14 Jun 2011 10:23:58 +0800
>> Kassey Lee <kassey1216@gmail.com> wrote:
>>
>>> Jon, Here is my comments.
>>
>> Thanks for having a look.
>>
>>>> +config VIDEO_CAFE_CCIC
>>>> + tristate "Marvell 88ALP01 (Cafe) CMOS Camera Controller support"
>>>> + depends on PCI && I2C && VIDEO_V4L2
>>>> + select VIDEO_OV7670
>>>>
>>> why need binds with sensor ? suppose CCIC driver and sensor driver are
>>> independent, even if your hardware only support OV7670
>>
>> We all agree that needs to change. This particular patch, though, is
>> concerned with moving a working driver into a new directory; making that
>> sort of functional change would not be appropriate here.
While cafe-ccic only supports ov7670, the above select is OK, as otherwise,
the driver won't be operational. After adding new sensors, however, the above
should be changed to:
select VIDEO_OV7670 if VIDEO_HELPER_CHIPS_AUTO
select VIDEO_FOO if VIDEO_HELPER_CHIPS_AUTO
select VIDEO_BAR if VIDEO_HELPER_CHIPS_AUTO
...
This way, if VIDEO_HELPER_CHIPS_AUTO is enabled, all the possible sensors
used with cafe-ccic will be selected.
>>
>>>> +#include <media/ov7670.h>
>>>>
>>> ccic would not be aware of the sensor name.
>>
>> Ditto.
>>
>> Thanks,
>>
>> jon
>>
>
>
>
next prev parent reply other threads:[~2011-06-15 11:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 17:46 Refactor cafe_ccic and add Armada 610 driver [V2] Jonathan Corbet
2011-06-11 17:46 ` [PATCH 1/8] marvell-cam: Move cafe-ccic into its own directory Jonathan Corbet
[not found] ` <BANLkTikXATbgOZQbzaj4sQEmELsdpNobfQ@mail.gmail.com>
2011-06-14 14:23 ` Jonathan Corbet
2011-06-15 2:01 ` Kassey Lee
2011-06-15 11:37 ` Mauro Carvalho Chehab [this message]
2011-06-11 17:46 ` [PATCH 2/8] marvell-cam: Separate out the Marvell camera core Jonathan Corbet
2011-06-14 2:58 ` Kassey Lee
2011-06-14 14:49 ` Jonathan Corbet
2011-06-16 2:30 ` Kassey Lee
2011-06-16 3:12 ` Kassey Lee
2011-06-16 15:27 ` Jonathan Corbet
2011-06-17 0:45 ` Mauro Carvalho Chehab
2011-06-17 3:11 ` Kassey Lee
2011-06-22 22:12 ` Jonathan Corbet
2011-06-27 9:23 ` Kassey Lee
2011-06-17 0:40 ` Mauro Carvalho Chehab
2011-06-17 2:51 ` Kassey Lee
2011-06-11 17:46 ` [PATCH 3/8] marvell-cam: Pass sensor parameters from the platform Jonathan Corbet
2011-06-11 17:46 ` [PATCH 4/8] marvell-cam: Remove the "untested" comment Jonathan Corbet
2011-06-11 17:46 ` [PATCH 5/8] marvell-cam: Move Cafe-specific register definitions to cafe-driver.c Jonathan Corbet
2011-06-11 17:46 ` [PATCH 6/8] marvell-cam: Right-shift i2c slave ID's in the cafe driver Jonathan Corbet
2011-06-17 0:51 ` Mauro Carvalho Chehab
2011-06-11 17:46 ` [PATCH 7/8] marvell-cam: Allocate the i2c adapter in the platform driver Jonathan Corbet
2011-06-11 17:46 ` [PATCH 8/8] marvell-cam: Basic working MMP camera driver Jonathan Corbet
2011-06-16 2:37 ` Kassey Lee
2011-06-16 15:17 ` Jonathan Corbet
2011-06-16 19:44 ` Sylwester Nawrocki
2011-06-17 1:15 ` 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=4DF8997A.8090007@infradead.org \
--to=mchehab@infradead.org \
--cc=corbet@lwn.net \
--cc=dsd@laptop.org \
--cc=g.liakhovetski@gmx.de \
--cc=kassey1216@gmail.com \
--cc=leiwen@marvell.com \
--cc=linux-media@vger.kernel.org \
--cc=qingx@marvell.com \
--cc=ygli@marvell.com \
--cc=ytang5@marvell.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.