On Friday 28 September 2012 01:09 PM, Maarten Lankhorst wrote:
Op 28-09-12 09:29, Rob Clark schreef:
From: Rob Clark
We never really clarified if unmap could be done in atomic context.
But since mapping might require sleeping, this implies mutex in use
to synchronize mapping/unmapping, so unma
On Fri, Sep 28, 2012 at 8:21 PM, Guennadi Liakhovetski
wrote:
> Hi Eric
>
> On Fri, 28 Sep 2012, Guennadi Liakhovetski wrote:
>
>> Hi Anatolij
>>
>> I can take this patch, but we need an ack from a PXA / ARM maintainer.
>
> Could we have your ack, please?
Yes, this looks completely good to me. So
On 09/28/2012 09:42 PM, Thomas Hellstrom wrote:
On 09/28/2012 04:14 PM, Maarten Lankhorst wrote:
Hey,
Op 28-09-12 14:41, Maarten Lankhorst schreef:
Documentation says that code requiring dma-buf should add it to
select, so inline fallbacks are not going to be used. A link error
will make it ob
On 09/28/2012 04:14 PM, Maarten Lankhorst wrote:
Hey,
Op 28-09-12 14:41, Maarten Lankhorst schreef:
Documentation says that code requiring dma-buf should add it to
select, so inline fallbacks are not going to be used. A link error
will make it obvious what went wrong, instead of silently doing
On Fri, Sep 28, 2012 at 2:31 PM, Antti Palosaari wrote:
> Hello,
> Did not fix the issue. Problem remains same. With the sleep + that patch it
> works still.
>
> On 09/28/2012 06:04 PM, Mauro Carvalho Chehab wrote:
>>
>> The tda18271 datasheet says:
>>
>> "The image rejection calibration a
On Fri, 2012-09-28 at 20:55 +0300, Antti Palosaari wrote:
> On 09/28/2012 07:34 PM, Damien Bally wrote:
> > > I will NACK that initially because that USB ID already used by AF9015
> >> driver. You have to explain / study what happens when AF9015 driver
> >> claims that device same time.
> >>
> >
Le 28/09/2012 19:55, Antti Palosaari a écrit :
I am not sure what you do here but let it be clear.
There is same ID used by af9015 and it913x. Both drivers are loaded when
that ID appears. What I understand *both* drivers, af9015 and it913x
should detect if device is correct or not. If device
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date:Fri Sep 28 19:00:22 CEST 2012
git hash:8928b6d1568eb9104cc9e2e6627d7086437b2fb3
gcc version: i686-linux-gcc (GC
Hi,
On 09/28/2012 08:37 PM, Albert Wang wrote:
>>> + ret = v4l2_subdev_call(sd, core, g_chip_ident,&id);
>
>> Yuck. Don't abuse this. g_chip_ident is for debugging purposes only.
>
> Yes, can remove it.
>
>>> + if (ret< 0) {
>>> + cam_err(mcam, "%s %d\n", __func__, __LINE__);
>>>
Hi, Hans
Thank you for reviewing the patches!
>>On Fri September 28 2012 15:47:20 Albert Wang wrote:
>>
>> This patch adds the support of Soc Camera on marvell-ccic mcam-core.
>> The Soc Camera mode does not compatible with current mode.
>> Only one mode can be used at one time.
>>
>> To use So
Hello,
Did not fix the issue. Problem remains same. With the sleep + that patch
it works still.
On 09/28/2012 06:04 PM, Mauro Carvalho Chehab wrote:
The tda18271 datasheet says:
"The image rejection calibration and RF tracking filter
calibration must be launched exactly as de
On 09/28/2012 07:34 PM, Damien Bally wrote:
> I will NACK that initially because that USB ID already used by AF9015
driver. You have to explain / study what happens when AF9015 driver
claims that device same time.
Hi Antti
With the Cinergy stick alone, dvb_usb_af9015 is predictably loaded,
On 09/28/2012 08:07 PM, Hans Verkuil wrote:
On Fri September 28 2012 17:30:05 Mauro Carvalho Chehab wrote:
Em Fri, 28 Sep 2012 16:21:35 +0200
Hans Verkuil escreveu:
On Fri September 28 2012 14:43:32 Hans Verkuil wrote:
Hi Antti,
Mauro asked me to look into LNA as well, in particular how thi
Hi,
Am 27.09.2012 21:41, schrieb Hans de Goede:
> Hi,
>
> On 09/27/2012 03:20 PM, Frank Schäfer wrote:
>
>
>
>>> What you've found is a qv4l2 bug (do you have the latest version?)
>>
>> Of course, I'm using the latest developer version.
>>
>> Even if this is just a qv4l2-bug: how do you want to f
On Fri September 28 2012 17:30:05 Mauro Carvalho Chehab wrote:
> Em Fri, 28 Sep 2012 16:21:35 +0200
> Hans Verkuil escreveu:
>
> > On Fri September 28 2012 14:43:32 Hans Verkuil wrote:
> > > Hi Antti,
> > >
> > > Mauro asked me to look into LNA as well, in particular how this could be
> > > don
Just giving a proper subject
-- Forwarded message --
From: Marcos Souza
Date: 2012/9/28
Subject: Build
To: linux-media@vger.kernel.org, linux-ker...@vger.kernel.org
Hi media guys,
After try to build the media drivers with some radios enabled, I got this error:
marcos@tux:/mnt
> I will NACK that initially because that USB ID already used by AF9015
driver. You have to explain / study what happens when AF9015 driver
claims that device same time.
Hi Antti
With the Cinergy stick alone, dvb_usb_af9015 is predictably loaded, but
doesn't prevent dvb_usb_it913x from work
On 09/28/2012 02:43 PM, Mauro Carvalho Chehab wrote:
Em Thu, 27 Sep 2012 17:58:24 -0400
Michael Krufky escreveu:
On Thu, Sep 27, 2012 at 5:38 PM, Antti Palosaari wrote:
On 09/28/2012 12:20 AM, Michael Krufky wrote:
Mike, There is other problem too. PCTV 520e, which is Em28xx + DRX-K +
TDA
Op 28-09-12 17:29, Thomas Hellström schreef:
> On 9/28/12 2:43 PM, Maarten Lankhorst wrote:
>> This adds support for a generic reservations framework that can be
>> hooked up to ttm and dma-buf and allows easy sharing of reservations
>> across devices.
>>
>> The idea is that a dma-buf and ttm objec
Em Fri, 28 Sep 2012 16:21:35 +0200
Hans Verkuil escreveu:
> On Fri September 28 2012 14:43:32 Hans Verkuil wrote:
> > Hi Antti,
> >
> > Mauro asked me to look into LNA as well, in particular how this could be
> > done
> > on the analog side as well.
Thanks for that!
> >
> > While reading thr
On 9/28/12 2:43 PM, Maarten Lankhorst wrote:
This adds support for a generic reservations framework that can be
hooked up to ttm and dma-buf and allows easy sharing of reservations
across devices.
The idea is that a dma-buf and ttm object both will get a pointer
to a struct reservation_object, w
Hi Laurent,
2012/9/28 Laurent Pinchart :
> Hi Enric,
>
> On Friday 28 September 2012 10:21:56 Enric Balletbò i Serra wrote:
>> 2012/9/28 Laurent Pinchart :
>> > On Thursday 27 September 2012 18:05:56 Enric Balletbò i Serra wrote:
>> >> 2012/9/27 Laurent Pinchart :
>> >> > On Wednesday 26 September
The tda18271 datasheet says:
"The image rejection calibration and RF tracking filter
calibration must be launched exactly as described in the
flowchart, otherwise bad calibration or even blocking of the
TDA18211HD can result making it impossible to communicate
On Fri September 28 2012 14:43:32 Hans Verkuil wrote:
> Hi Antti,
>
> Mauro asked me to look into LNA as well, in particular how this could be done
> on the analog side as well.
>
> While reading through this patch I noticed that the new property was added to
> dtv_property_process_set, but not t
This driver adds basic support for Aptina ar0130 1.2M sensor.
Changes for v2:
1: Include new test pattern control as pointed by Hans and Lad.
2: Remove soc_camera.h as suggested by Guennadi.
3: Change auto exposure control as pointed by Dan Rittersdorf.
4: Change incorrect return value as pointed
On Fri September 28 2012 15:47:20 Albert Wang wrote:
> From: Libin Yang
>
> This patch adds the support of Soc Camera on marvell-ccic mcam-core.
> The Soc Camera mode does not compatible with current mode.
> Only one mode can be used at one time.
>
> To use Soc Camera, CONFIG_VIDEO_MMP_SOC_CAMER
Hey,
Op 28-09-12 14:41, Maarten Lankhorst schreef:
> Documentation says that code requiring dma-buf should add it to
> select, so inline fallbacks are not going to be used. A link error
> will make it obvious what went wrong, instead of silently doing
> nothing at runtime.
>
The whole patch s
This patch adds support of 3 frame buffers in DMA-contiguous mode.
In current DMA_CONTIG mode, only 2 frame buffers can be supported.
Actually, Marvell CCIC can support at most 3 frame buffers.
Currently 2 frame buffers mode will be used by default.
To use 3 frame buffers mode, can do:
define M
From: Libin Yang
This patch adds the support of Soc Camera on marvell-ccic mmp-driver.
The Soc Camera mode does not compatible with current mode.
Only one mode can be used at one time.
To enable Soc Camera on mmp:
In Device Drivers --> Multimedia support:
select Cameras/video grabbers support
From: Libin Yang
This patch adds the support of Soc Camera on marvell-ccic mcam-core.
The Soc Camera mode does not compatible with current mode.
Only one mode can be used at one time.
To use Soc Camera, CONFIG_VIDEO_MMP_SOC_CAMERA should be defined.
What's more, the platform driver should suppor
From: Libin Yang
This patch adds the definition of CCIC1/2 Clock Reset register address
Signed-off-by: Albert Wang
Signed-off-by: Libin Yang
---
arch/arm/mach-mmp/include/mach/regs-apmu.h |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-mmp/include/mach
The following patches series will add soc camera support on marvell-ccic
[PATCH 1/4] [media] mmp: add register definition for marvell ccic
[PATCH 2/4] [media] marvell-ccic: core: add soc camera support on marvell-ccic
mcam-core
[PATCH 3/4] [media] marvell-ccic: mmp: add soc camera support on ma
On Fri, 28 Sep 2012 15:30:33 +0200 (CEST)
Guennadi Liakhovetski wrote:
...
> > Yes. But i.e. the driver calling the sub-device stream control function
> > on streamon knows that the normal mode is not supported and therefore it
> > calls this function with argument enable == 0, effectively setting
On Fri, 28 Sep 2012, Anatolij Gustschin wrote:
> Hi Guennadi,
>
> On Fri, 28 Sep 2012 14:33:34 +0200 (CEST)
> Guennadi Liakhovetski wrote:
> ...
> > > @@ -235,12 +238,32 @@ static int mt9v022_s_stream(struct v4l2_subdev *sd,
> > > int enable)
> > > struct i2c_client *client = v4l2_get_subdevd
Dear developers,
Due to some temporary trouble, I was unable to receive emails from
linux-media, since 10 hours ago. As I use my IMAP box to check for
review e-mails, if you replied to an existing patch during that period
of time, and didn't answered it with a Nacked-by/Acked-by tag[1],
please pin
On Fri, Sep 28, 2012 at 02:41:48PM +0200, Maarten Lankhorst wrote:
> Documentation says that code requiring dma-buf should add it to
> select, so inline fallbacks are not going to be used. A link error
> will make it obvious what went wrong, instead of silently doing
> nothing at runtime.
>
> Sign
Hi Guennadi,
On Fri, 28 Sep 2012 14:33:34 +0200 (CEST)
Guennadi Liakhovetski wrote:
...
> > @@ -235,12 +238,32 @@ static int mt9v022_s_stream(struct v4l2_subdev *sd,
> > int enable)
> > struct i2c_client *client = v4l2_get_subdevdata(sd);
> > struct mt9v022 *mt9v022 = to_mt9v022(client);
This adds support for a generic reservations framework that can be
hooked up to ttm and dma-buf and allows easy sharing of reservations
across devices.
The idea is that a dma-buf and ttm object both will get a pointer
to a struct reservation_object, which has to be reserved before
anything is done
Documentation says that code requiring dma-buf should add it to
select, so inline fallbacks are not going to be used. A link error
will make it obvious what went wrong, instead of silently doing
nothing at runtime.
Signed-off-by: Maarten Lankhorst
---
include/linux/dma-buf.h | 99 -
Signed-off-by: Maarten Lankhorst
---
The self-tests will fail if the commit "lockdep: Check if nested
lock is actually held" from linux tip core/locking is not applied.
---
drivers/base/reservation.c | 46 +-
include/linux/reservation.h | 29 +++-
lib/Kconfig.debug |1
l
A fence can be attached to a buffer which is being filled or consumed
by hw, to allow userspace to pass the buffer without waiting to another
device. For example, userspace can call page_flip ioctl to display the
next frame of graphics after kicking the GPU but while the GPU is still
rendering. T
This type of fence can be used with hardware synchronization for simple
hardware that can block execution until the condition
(dma_buf[offset] - value) >= 0 has been met.
A software fallback still has to be provided in case the fence is used
with a device that doesn't support this mechanism. It is
This brings both ds3000_readreg() and ds3000_tuner_readreg() in line
with ds3000_writereg() and ds3000_tuner_writereg() respectively.
Signed-off-by: Rémi Cardona
---
drivers/media/dvb-frontends/ds3000.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/drivers/med
Signed-off-by: Rémi Cardona
---
drivers/media/dvb-frontends/ds3000.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/dvb-frontends/ds3000.c
b/drivers/media/dvb-frontends/ds3000.c
index 4c8ac26..46874c7 100644
--- a/drivers/media/dvb-frontends/ds3000.c
+++ b/drivers/media/dvb
ds3000_readreg() returns negative values in case of i2c failures. The
old code would simply return 0 when failing to read the 0xb2 register,
misleading ds3000_initfe() into believing that the firmware had been
correctly loaded.
Signed-off-by: Rémi Cardona
---
drivers/media/dvb-frontends/ds3000.c
- if kmalloc() returns NULL, we can return immediately without trying
to kfree() a NULL pointer.
- if i2c_transfer() fails, error out immediately instead of trying to
upload the remaining bytes of the firmware.
- the error code is then properly propagated down to ds3000_initfe().
Signed-o
Since b9bf2eafaad9c1ef02fb3db38c74568be601a43a, the function
ds3000_firmware_ondemand() is called only once during init. This
locking scheme may have been useful when the firmware was loaded at
each tune.
Furthermore, it looks like this 'lock' was put in to prevent concurrent
access (and not recur
Hi all,
Here's hopefully the final round of patches for ds3000.
All of the patches have been rebased on top of today's staging/for_v3.7
branch.
Patches 1 through 4 are identical to the previous v2. Patches 5 and 6
are functionally identical, only the printk()s have been removed. Patch
7 is new,
Signed-off-by: Rémi Cardona
---
drivers/media/usb/dvb-usb/dw2102.c | 36 ++--
1 file changed, 26 insertions(+), 10 deletions(-)
diff --git a/drivers/media/usb/dvb-usb/dw2102.c
b/drivers/media/usb/dvb-usb/dw2102.c
index 9382895..937c744 100644
--- a/drivers/medi
Signed-off-by: Rémi Cardona
---
drivers/media/dvb-frontends/ds3000.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/media/dvb-frontends/ds3000.c
b/drivers/media/dvb-frontends/ds3000.c
index 59184a8..c66d731 100644
--- a/drivers/media/dvb-frontends/ds3000.c
++
Hi Hans,
On Fri, Sep 28, 2012 at 6:22 PM, Hans Verkuil wrote:
> Hi Prabhakar!
>
> On Fri September 28 2012 14:44:59 Prabhakar Lad wrote:
>> Hi Kevin,
>>
>> On Wed, Aug 8, 2012 at 6:00 PM, Prabhakar Lad wrote:
>> > From: Hans Verkuil
>> >
>> > Signed-off-by: Hans Verkuil
>> > Signed-off-by: Lad
Hi Prabhakar!
On Fri September 28 2012 14:44:59 Prabhakar Lad wrote:
> Hi Kevin,
>
> On Wed, Aug 8, 2012 at 6:00 PM, Prabhakar Lad wrote:
> > From: Hans Verkuil
> >
> > Signed-off-by: Hans Verkuil
> > Signed-off-by: Lad, Prabhakar
> > Signed-off-by: Manjunath Hadli
> > ---
> > arch/arm/mach
A recent commit "[media] v4l2: make vidioc_s_crop const" introduced
warnings in mx2_camera. Fix them by cleanly separating writable and
read-only variables in cropping operations.
Signed-off-by: Guennadi Liakhovetski
---
drivers/media/platform/soc_camera/mx2_camera.c |5 +++--
1 files change
A recent commit "[media] v4l2: make vidioc_s_crop const" introduced
warnings in sh_mobile_ceu_camera. Fix them by cleanly separating writable
and read-only variables in cropping operations.
Signed-off-by: Guennadi Liakhovetski
---
.../platform/soc_camera/sh_mobile_ceu_camera.c | 13 +++
.set_crop() implementation in mx1_camera is identical with the default.
Remove the copy to switch to using the default stab.
Signed-off-by: Guennadi Liakhovetski
---
drivers/media/platform/soc_camera/mx1_camera.c |9 -
1 files changed, 0 insertions(+), 9 deletions(-)
diff --git a/dr
These patches fix warnings, added by the recent commit
commit 4f996594ceaf6c3f9bc42b40c40b0f7f87b79c86
Author: Hans Verkuil
Date: Wed Sep 5 05:10:48 2012 -0300
[media] v4l2: make vidioc_s_crop const
If there are no objections, I'll include them in my (hopefully) last
3.7-merge pull reques
A recent commit "[media] v4l2: make vidioc_s_crop const" introduced
warnings in omap1_camera. Fix them by adjusting a function declaration.
Signed-off-by: Guennadi Liakhovetski
---
drivers/media/platform/soc_camera/omap1_camera.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
dif
A recent commit "[media] v4l2: make vidioc_s_crop const" introduced
warnings in sh_vou. Fix them by cleanly separating writable and
read-only variables in cropping operations.
Signed-off-by: Guennadi Liakhovetski
---
drivers/media/platform/sh_vou.c |3 ++-
1 files changed, 2 insertions(+), 1
A recent commit "[media] v4l2: make vidioc_s_crop const" introduced
warnings in mx3_camera. Fix them by cleanly separating writable and
read-only variables in cropping operations.
Signed-off-by: Guennadi Liakhovetski
---
drivers/media/platform/soc_camera/mx3_camera.c |5 +++--
1 files change
A recent commit "[media] v4l2: make vidioc_s_crop const" introduced
warnings in pxa_camera.c. Fix them by adjusting a function declaration.
Signed-off-by: Guennadi Liakhovetski
---
drivers/media/platform/soc_camera/pxa_camera.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff
Hi Kevin,
On Wed, Aug 8, 2012 at 6:00 PM, Prabhakar Lad wrote:
> From: Hans Verkuil
>
> Signed-off-by: Hans Verkuil
> Signed-off-by: Lad, Prabhakar
> Signed-off-by: Manjunath Hadli
> ---
> arch/arm/mach-davinci/board-dm644x-evm.c | 15 ++--
> arch/arm/mach-davinci/dm644x.c |
Hi Antti,
Mauro asked me to look into LNA as well, in particular how this could be done
on the analog side as well.
While reading through this patch I noticed that the new property was added to
dtv_property_process_set, but not to dtv_property_process_get. Can you look
into that and add 'get' sup
Hi Anatolij
On Fri, 28 Sep 2012, Anatolij Gustschin wrote:
> Some camera systems cannot operate mt9v022 in normal mode and use
> only the snapshot mode. The TechNote for mt9v022 (TN0960) and mt9v024
> (TN-09-225) describes required register settings when configuring the
> snapshot operation. The
Hi Eric
On Fri, 28 Sep 2012, Guennadi Liakhovetski wrote:
> Hi Anatolij
>
> I can take this patch, but we need an ack from a PXA / ARM maintainer.
Could we have your ack, please?
Thanks
Guennadi
> On Fri, 28 Sep 2012, Anatolij Gustschin wrote:
>
> > Set "y_skip_top" to zero and revise commen
Hi Anatolij
I can take this patch, but we need an ack from a PXA / ARM maintainer.
Thanks
Guennadi
On Fri, 28 Sep 2012, Anatolij Gustschin wrote:
> Set "y_skip_top" to zero and revise comment as I do not see this line
> corruption on two different mt9v022 setups. The first read-out line
> is pe
Em Thu, 27 Sep 2012 17:58:24 -0400
Michael Krufky escreveu:
> On Thu, Sep 27, 2012 at 5:38 PM, Antti Palosaari wrote:
> > On 09/28/2012 12:20 AM, Michael Krufky wrote:
> > Mike, There is other problem too. PCTV 520e, which is Em28xx + DRX-K +
> > TDA18271, fails to attach tuner now. Tuner is wi
Reviewed-by: Hans Verkuil
Signed-off-by: Hans Verkuil
Signed-off-by: Javier Martin
---
drivers/media/platform/marvell-ccic/mcam-core.c | 54 ---
drivers/media/platform/marvell-ccic/mcam-core.h |2 +
2 files changed, 11 insertions(+), 45 deletions(-)
diff --git a/drive
And added a missing kfree to clean up the via_camera struct.
Reviewed-by: Hans Verkuil
Signed-off-by: Hans Verkuil
Signed-off-by: Javier Martin
---
drivers/media/platform/via-camera.c | 60 ---
1 file changed, 14 insertions(+), 46 deletions(-)
diff --git a/dr
via-camera and mcam-core were the only bridge drivers that used ov7670.
Since now they have been moved to use the ctrl framework, the old
legacy callbacks in the ov7670 can be removed.
Reviewed-by: Hans Verkuil
Signed-off-by: Javier Martin
---
drivers/media/i2c/ov7670.c |7 ---
1 file c
Reviewed-by: Hans Verkuil
Signed-off-by: Javier Martin
---
Changes since v2:
- Do not use 'cur.val' to get gain value.
---
drivers/media/i2c/ov7670.c | 310
1 file changed, 112 insertions(+), 198 deletions(-)
diff --git a/drivers/media/i2c/ov7670.
The following series migrate ov7670 sensor and current users to ctrl framework
as discussed in [1]. This has been tested against mx2_camera soc-camera bridge,
so tests or acks will be required from people using cam-core and via-camera out
there.
This will have to be applied on top of my previous
Changes since RFCv1:
- Improved the commit text
- Changed 'if (t->audmode > V4L2_TUNER_MODE_STEREO)' as suggested by Mauro.
- Update t->audmode after having called the tuner driver, allowing the tuner
driver to modify audmode if it only supports mono.
Regards,
Hans
--
To unsubscribe f
From: Hans Verkuil
Fixes a v4l2-compliance error: setting audmode to a value other than mono
or stereo for a radio device should map to MODE_STEREO.
The spec specifies that for radio devices only mono and stereo audmodes are
valid. If the user specifies another audmode in v4l2_tuner, then that s
Hi Anatolij
On Fri, 28 Sep 2012, Anatolij Gustschin wrote:
> With mpc52xx_csi interface I2C subdev streamon after vb2_streamon()
> doesn't work due to mpc52xx sensor interface glue-logic restrictions.
>
> Since mpc5200 doesn't have a camera sensor interface, the sensor on
> O2D cameras is connec
Hi Hans,
On 28 September 2012 13:05, Hans Verkuil wrote:
> On Fri September 28 2012 12:50:55 Javier Martin wrote:
>> Signed-off-by: Hans Verkuil
>> Signed-off-by: Javier Martin
>> ---
>> Changes since v1:
>> - Use v4l2_ctrl_auto_cluster() for auto_gain and auto_exp.
>>
>> ---
>> drivers/media
This pull request adds two new features to the control framework:
- a notify function that is needed to have a bridge driver be notified of
subdevice control changes
- a new filter function to have more control over which controls are added
by v4l2_ctrl_add_handler.
Both of these features are
On Fri September 28 2012 12:50:55 Javier Martin wrote:
> Signed-off-by: Hans Verkuil
> Signed-off-by: Javier Martin
> ---
> Changes since v1:
> - Use v4l2_ctrl_auto_cluster() for auto_gain and auto_exp.
>
> ---
> drivers/media/i2c/ov7670.c | 310
>
of_*_cmp() macros do not depend on any OF functions and can be defined also
if CONFIG_OF isn't set. Also include linux/string.h, required by those
macros.
Signed-off-by: Guennadi Liakhovetski
---
These definitions are also required for "# CONFIG_OF is not set" builds.
include/linux/of.h | 15
via-camera and mcam-core were the only bridge drivers that used ov7670.
Since now they have been moved to use the ctrl framework, the old
legacy callbacks in the ov7670 can be removed.
Signed-off-by: Javier Martin
---
drivers/media/i2c/ov7670.c |7 ---
1 file changed, 7 deletions(-)
dif
And added a missing kfree to clean up the via_camera struct.
Signed-off-by: Hans Verkuil
Signed-off-by: Javier Martin
---
drivers/media/platform/via-camera.c | 60 ---
1 file changed, 14 insertions(+), 46 deletions(-)
diff --git a/drivers/media/platform/via-ca
Signed-off-by: Hans Verkuil
Signed-off-by: Javier Martin
---
drivers/media/platform/marvell-ccic/mcam-core.c | 54 ---
drivers/media/platform/marvell-ccic/mcam-core.h |2 +
2 files changed, 11 insertions(+), 45 deletions(-)
diff --git a/drivers/media/platform/marvell-c
Signed-off-by: Hans Verkuil
Signed-off-by: Javier Martin
---
Changes since v1:
- Use v4l2_ctrl_auto_cluster() for auto_gain and auto_exp.
---
drivers/media/i2c/ov7670.c | 310
1 file changed, 112 insertions(+), 198 deletions(-)
diff --git a/driver
The following series migrate ov7670 sensor and current users to ctrl framework
as discussed in [1]. This has been tested against mx2_camera soc-camera bridge,
so tests or acks will be required from people using cam-core and via-camera out
there.
This will have to be applied on top of my previous
PULL request updated, contains now 3 fc2580 driver fixes from Gianluca
Gennari. Could you handle these quickly :)
The following changes since commit 8928b6d1568eb9104cc9e2e6627d7086437b2fb3:
[media] media: mx2_camera: use managed functions to clean up code
(2012-09-27 15:56:47 -0300)
are
From: Jeongtae Park
Adds register definitions for MFC v6.x firmware
Signed-off-by: Jeongtae Park
Signed-off-by: Janghyuck Kim
Signed-off-by: Jaeryul Oh
Signed-off-by: Naveen Krishna Chatradhi
Signed-off-by: Arun Kumar K
---
drivers/media/platform/s5p-mfc/regs-mfc-v6.h | 408 ++
MFC variant data replaces various macros used in the driver
which will change in a different version of MFC hardware.
Also does a cleanup of MFC context structure and common files.
Signed-off-by: Jeongtae Park
Signed-off-by: Janghyuck Kim
Signed-off-by: Jaeryul Oh
Signed-off-by: Naveen Krishna
New controls are added for supporting H264 encoding features like
- MVC frame packing
- Flexible macroblock ordering
- Arbitrary slice ordering
- Hierarchial coding
Signed-off-by: Jeongtae Park
Signed-off-by: Naveen Krishna Chatradhi
Signed-off-by: Arun Kumar K
---
Documentation/DocBook/media/
Adds the following new fourcc definitions.
For multiplanar YCbCr
- V4L2_PIX_FMT_NV21M
- V4L2_PIX_FMT_NV12MT_16X16
and compressed formats
- V4L2_PIX_FMT_H264_MVC
- V4L2_PIX_FMT_VP8
Signed-off-by: Jeongtae Park
Signed-off-by: Naveen Krishna Chatradhi
Signed-off-by:
The patchset adds support for MFCv6 firmware in s5p-mfc driver.
The patches are rebased to the latest media-tree.
Changelog v7
- Removed unused macros from register files
Changelog v6
- Use s5p_mfc_hw_call macro to call all HW related ops and cmds
- Rebased onto latest media-tree
- Resending patc
A simplified version of the semantic patch that finds this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@r1@
statement S;
position p,p1;
@@
S@p1;@p
@script:python r2@
p << r1.p;
p1 << r1.p1;
@@
if p[0].line != p1[0].line_end:
cocci.include_match(False)
@@
position r1.p;
@@
-;@p
On 09/28/2012 11:21 AM, Kamil Debski wrote:
>> -Original Message-
>> From: Sachin Kamat [mailto:sachin.ka...@linaro.org]
>> Sent: 28 September 2012 09:02
>> To: linux-media@vger.kernel.org
>> Cc: k.deb...@samsung.com; s.nawro...@samsung.com; sachin.ka...@linaro.org;
>> patc...@linaro.org
>>
From: Hans Verkuil
length should be set to num_planes in __fill_v4l2_buffer(). That way the
caller knows how many planes there are in the buffer.
Signed-off-by: Hans Verkuil
---
drivers/media/v4l2-core/videobuf2-core.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/v4l2-c
Changes since RFCv1:
- Don't move num_planes to vb2_queue. In certain circumstances it is possible
to have buffers with different number of planes, so keep num_planes in
vb2_buffer. This complicated vb2_dqbuf a bit since the plane verification
now has to be done just before the buffer is deq
From: Hans Verkuil
The core code for PREPARE_BUF didn't take the multiplanar case into account,
which might cause page faults. Handle PREPARE_BUF just like QUERYBUF and
QBUF/DQBUF.
Signed-off-by: Hans Verkuil
---
drivers/media/v4l2-core/v4l2-ioctl.c |1 +
1 file changed, 1 insertion(+)
di
From: Hans Verkuil
The plane verification should be done before actually queuing or
dequeuing buffers, so move it out of __fill_v4l2_buffer and __fill_vb_buffer
and call it as a separate step.
This also makes it possible to change the return type of __fill_v4l2/vb_buffer
to void.
The dqbuf case
From: Hans Verkuil
Clarify the behavior of v4l2_buffer in the multiplanar case,
including fixing a false statement: you can't set m.planes to NULL
when calling DQBUF.
Signed-off-by: Hans Verkuil
---
Documentation/DocBook/media/v4l/io.xml |6 --
Documentation/DocBook/media/
Hi Sachin,
Thank you for your patch, fixing this bug and testing suspend/resume.
Best wishes,
--
Kamil Debski
Linux Platform Group
Samsung Poland R&D Center
> -Original Message-
> From: Sachin Kamat [mailto:sachin.ka...@linaro.org]
> Sent: 28 September 2012 09:02
> To: linux-media@vger.
With mpc52xx_csi interface I2C subdev streamon after vb2_streamon()
doesn't work due to mpc52xx sensor interface glue-logic restrictions.
Since mpc5200 doesn't have a camera sensor interface, the sensor on
O2D cameras is connected to the LocalPlus bus by special glue-logic.
While sensor read-out t
IFM O2D cameras use special sensor bus interface glue-logic to
connect camera sensors to mpc5200 LocalPlus bus. Add camera
sensor driver for this mpc5200 camera interface.
Signed-off-by: Anatolij Gustschin
---
drivers/media/platform/soc_camera/Kconfig |7 +
drivers/media/platform/so
Hi Hans,
On 28 September 2012 10:23, Hans Verkuil wrote:
> On Fri September 28 2012 09:48:01 Javier Martin wrote:
>> static const struct v4l2_subdev_core_ops ov7670_core_ops = {
>> .g_chip_ident = ov7670_g_chip_ident,
>> - .g_ctrl = ov7670_g_ctrl,
>> - .s_ctrl = ov7670_s_ctrl,
>> -
1 - 100 of 113 matches
Mail list logo
