Sorry for resurrecting this thread but I'm still quite interested on
making this scenario work:
> OK, I've performed some tests with several resolutions and gop sizes,
here is the table with the results:
>
> Always playing 3 streams
>
> | Resolution | QP | GopSize | Kind of content |
Hello Philipp,
On 14/03/18 16:11, Philipp Zabel wrote:
Hi Javier,
On Wed, 2018-03-14 at 15:35 +0100, Javier Martin wrote:
[...]
The encoder is running on a different system with an older 4.1.0 kernel.
Altough the firmware version in the code is 3.1.1 as well.
Do you think I should try
Hello,
On 14/03/18 14:57, Philipp Zabel wrote:
On Wed, 2018-03-14 at 13:05 +0100, Javier Martin wrote:
Sorry everyone about my previous e-mail with all the HTML garbage. Here
is the plain text answer instead.
Hi Philipp,
thanks for your answer.
On 13/03/18 12:20, Philipp Zabel wrote
Sorry everyone about my previous e-mail with all the HTML garbage. Here
is the plain text answer instead.
Hi Philipp,
thanks for your answer.
On 13/03/18 12:20, Philipp Zabel wrote:
> Hi Javier,
>
> On Mon, 2018-03-12 at 17:54 +0100, Javier Martin wrote:
>> Hi,
>> we hav
Hi,
we have an i.MX6 Solo based board running the latest mainline kernel
(4.15.3).
As part of our development we were measuring the decoding performance of
the i.MX6 coda chip.
For that purpose we are feeding the decoder with 640x368 @ 30fps H.264
streams that have been generated by
The ov5640 sensor from Omnivision supports up to 2592x1944
and both CSI and MIPI interfaces.
The following driver adds support for the CSI interface only
and VGA, 720p resolutions at 30fps.
Signed-off-by: Javier Martin <javiermar...@by.com.es>
---
.../devicetree/bindings/media/i2c/ov56
Sorry for the unrelated patches,
I will submit this again.
On 30/09/15 09:34, Javier Martin wrote:
The ov5640 sensor from Omnivision supports up to 2592x1944
and both CSI and MIPI interfaces.
The following driver adds support for the CSI interface only
and VGA, 720p resolutions at 30fps
The ov5640 sensor from Omnivision supports up to 2592x1944
and both CSI and MIPI interfaces.
The following driver adds support for the CSI interface only
and VGA, 720p resolutions at 30fps.
Signed-off-by: Javier Martin <javiermar...@by.com.es>
---
.../devicetree/bindings/media/i2c/ov56
Hi,
we want to a v4l2 driver for the ov5640 sensor from Omnivision.
AFAIK, there was an attempt in the past to mainline that driver [1] but
it didn't make it in the end.
Some people were asking for the code for the ov5640 and the ov5642 to be
merged [2] as well but IMHO both sensors are not
Hi,
I am using mainline kernel 4.1 and I was writing a small application
that uses double buffering to read YUV420 frames from a file at 30fps
and displays them using the overlay plane in the imx-drm driver.
The first issue I noticed is that the image was green so I had to apply
the
Sorry for sending this to the wrong list.
On 07/08/15 09:25, Javier Martin wrote:
Hi,
I am using mainline kernel 4.1 and I was writing a small application
that uses double buffering to read YUV420 frames from a file at 30fps
and displays them using the overlay plane in the imx-drm driver
Hi Philipp,
thanks for your fast answer.
Apparently, the firmware is being loaded properly although it complains
about that version not being supported.
After queuing some YUV420 buffers with a simple application I perform a
VIDIOC_STREAMON in both the CAPTURE and the OUTPUT interfaces but I
Hello,
I am running kernel 4.1 in a var-dvk-solo-linux evaluation board from
Variscite.
This is what I get at system start-up:
coda 204.vpu: Firmware code revision: 34588
coda 204.vpu: Initialized CODA960.
coda 204.vpu: Unsupported firmware version: 2.1.8
coda 204.vpu: codec
Hello,
we have an BD-SL-i.MX6 platform (compatible with the Nitrogen6X) where
we are currently running the BSP from Freescale, which is based on
kernel 3.10 if I recall properly.
We are aware that those drivers have some issues, specially when it
comes to compliance with the V4L2 frameworks
, V4L2_CID_EXPOSURE,
+ 1, 0x, 1, 0x219);
v4l2_ctrl_new_std(mt9m111-hdl, mt9m111_ctrl_ops,
V4L2_CID_VFLIP, 0, 1, 1, 0);
v4l2_ctrl_new_std(mt9m111-hdl, mt9m111_ctrl_ops,
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S
this.
Guennadi might be able to give you a bit more information about the current
status.
So what kind of changes are required to make this work? Are we talking
about migrating each soc-camera sensor separately, soc-camera
framework changes, both of them?
--
Javier Martin
Vista Silicon S.L
Hi Guernnadi, Christoph,
On 12 March 2013 09:25, Christoph Fritz chf.fr...@googlemail.com wrote:
On Tue, 2013-03-12 at 08:58 +0100, Guennadi Liakhovetski wrote:
On Thu, 7 Mar 2013, javier Martin wrote:
What mbus format are you using? Could you please check if the s_width
value that your
On 12 March 2013 10:39, Guennadi Liakhovetski g.liakhovet...@gmx.de wrote:
On Tue, 12 Mar 2013, javier Martin wrote:
Hi Guernnadi, Christoph,
On 12 March 2013 09:25, Christoph Fritz chf.fr...@googlemail.com wrote:
On Tue, 2013-03-12 at 08:58 +0100, Guennadi Liakhovetski wrote:
On Thu, 7
omap_install_iommu_arch(omap2_iommu_ops);
}
module_init(omap2_iommu_init);
Does anyone know what could be the reason?
Regards.
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942 25 32 60
www.vista-silicon.com
--
To unsubscribe from
colour quality.
If Aptina comes up with better settings or I find them I'll post a
patch for you to test.
Regards.
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942 25 32 60
www.vista-silicon.com
--
To unsubscribe
.
However, according to the previous thread, omap3isp register should
return error but an oops should not be generated. So I think there is
a bug here anyway.
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942 25 32 60
Hi Laurent,
thank you for your answer.
On 11 March 2013 16:01, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
Hi Javier,
On Monday 11 March 2013 13:18:12 javier Martin wrote:
I've just found the following thread where te problem is explained:
http://lists.infradead.org/pipermail
whether the grey layer effect still
persists.
I will try to contact Aptina's technical support but, according to my
previous experience, there is no guarantee we get a clarifying answer.
I'll keep you updated nevertheless.
Regards.
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
= mt9m111_s_power(mt9m111-subdev, 1);
if (ret 0)
return ret;
Regards.
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942 25 32 60
www.vista-silicon.com
--
To unsubscribe from this list: send
if the s_width
value that your sensor mt9m001 returns is correct? Remember it should
be in pixels, not in bytes.
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942 25 32 60
www.vista-silicon.com
--
To unsubscribe from
.
Tested-By: Javier Martin javier.mar...@vista-silicon.com
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942 25 32 60
www.vista-silicon.com
--
To unsubscribe from this list: send the line unsubscribe linux-media
Hi Benoît,
thank you for your answer.
On 7 March 2013 13:13, Benoît Thébaudeau benoit.thebaud...@advansee.com wrote:
Dear Javier Martin,
On Thursday, March 7, 2013 10:43:42 AM, Javier Martin wrote:
Hi,
I am testing mt9m131 sensor (which is supported in mt9m111.c) in
mainline kernel 3.8
:
ov7670: remove legacy ctrl callbacks. (2013-01-29 12:21:40 +0100)
Javier Martin (9):
media: ov7670: add support for ov7675.
media: ov7670: make try_fmt() consistent with 'min_height' and
'min_width'.
media: ov7670
it to define a new v4l2-ctrl for this or should I use a
private ctrl instead?
Regards.
[1] http://calise.sourceforge.net/wordpress/
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942 25 32 60
www.vista
imx25-camera.0: MX2 Camera (CSI) driver probed, clock
frequency: 2216
Could we please keep the mx25 support?
That's great. Did you need to change anything in the mx2 camera driver
for mx25 to work? Have you already submitted the patches?
Regards.
--
Javier Martin
Vista Silicon S.L.
CDTUC
Hi Fabio,
On 2 January 2013 13:25, Fabio Estevam feste...@gmail.com wrote:
Hi Javier,
On Wed, Jan 2, 2013 at 10:18 AM, javier Martin
javier.mar...@vista-silicon.com wrote:
That's great. Did you need to change anything in the mx2 camera driver
for mx25 to work? Have you already submitted
On 16 November 2012 13:48, Sascha Hauer s.ha...@pengutronix.de wrote:
On Mon, Nov 05, 2012 at 04:59:44PM +0100, Javier Martin wrote:
Add support for IRAM to i.MX27 non-DT platforms using
iram_init() function.
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
arch/arm/mach
Add support for IRAM to i.MX27 non-DT platforms using
iram_init() function.
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
arch/arm/mach-imx/mm-imx27.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/mach-imx/mm-imx27.c b/arch/arm/mach-imx/mm-imx27.c
index
Use this helper function instead of hardcoding the
physical address of the IRAM in the i.MX27.
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media/video/Kconfig |2 +-
drivers/media/video/coda.c | 18 ++
2 files changed, 11 insertions(+), 9
[PATCH 1/4] media: mx2_camera: Remove i.mx25 support.
[PATCH 2/4] media: mx2_camera: Add image size HW limits.
[PATCH 3/4] media: mx2_camera: Remove 'buf_cleanup' callback.
[PATCH 4/4] media: mx2_camera: Remove buffer states.
--
To unsubscribe from this list: send the line unsubscribe linux-media
i.MX25 support has been broken for several releases
now and nobody seems to care about it.
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media/platform/soc_camera/mx2_camera.c | 405 ++--
1 file changed, 100 insertions(+), 305 deletions(-)
diff
The CSI has some constraints regarding image with.
This patch makes sure those requirements are met
in try_fmt().
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media/platform/soc_camera/mx2_camera.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff
All necessary tasks to end the streaming properly are
already implemented in mx2_stop_streaming() and nothing
remains to be done in this callback.
Furthermore, it only included debug messages so it can
be removed.
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media
After removing i.mx25 support and buf_cleanup() callback,
buffer states are not used in the code any longer.
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media/platform/soc_camera/mx2_camera.c | 11 ---
1 file changed, 11 deletions(-)
diff --git a/drivers
Hi Guennadi, Fabio,
On 30 October 2012 13:29, Guennadi Liakhovetski g.liakhovet...@gmx.de wrote:
On Tue, 30 Oct 2012, Fabio Estevam wrote:
Javier,
On Tue, Oct 30, 2012 at 10:16 AM, Javier Martin
javier.mar...@vista-silicon.com wrote:
i.MX25 support has been broken for several releases
Changes since v1:
- Remove i.MX25 support in the Kconfig file too in patch 1.
[PATCH v2 1/4] media: mx2_camera: Remove i.mx25 support.
[PATCH v2 2/4] media: mx2_camera: Add image size HW limits.
[PATCH v2 3/4] media: mx2_camera: Remove 'buf_cleanup' callback.
[PATCH v2 4/4] media: mx2_camera:
i.MX25 support has been broken for several releases
now and nobody seems to care about it.
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media/platform/soc_camera/Kconfig |7 +-
drivers/media/platform/soc_camera/mx2_camera.c | 405 ++--
2
The CSI has some constraints regarding image with.
This patch makes sure those requirements are met
in try_fmt().
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media/platform/soc_camera/mx2_camera.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff
All necessary tasks to end the streaming properly are
already implemented in mx2_stop_streaming() and nothing
remains to be done in this callback.
Furthermore, it only included debug messages so it can
be removed.
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media
After removing i.mx25 support and buf_cleanup() callback,
buffer states are not used in the code any longer.
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media/platform/soc_camera/mx2_camera.c | 11 ---
1 file changed, 11 deletions(-)
diff --git a/drivers
Default value should be 'debugging disabled'.
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media/platform/m2m-deinterlace.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/platform/m2m-deinterlace.c
b/drivers/media/platform/m2m
On 30 October 2012 15:57, Guennadi Liakhovetski g.liakhovet...@gmx.de wrote:
On Tue, 30 Oct 2012, javier Martin wrote:
Hi Guennadi, Fabio,
On 30 October 2012 13:29, Guennadi Liakhovetski g.liakhovet...@gmx.de
wrote:
On Tue, 30 Oct 2012, Fabio Estevam wrote:
Javier,
On Tue, Oct 30
4x gain ceiling is not enough to capture a decent image in conditions
of total darkness and only a LED light source. Allow a maximum gain
of 32x instead.
This doesn't have any drawback since the image quality in 'normal'
light conditions is the same.
Signed-off-by: Javier Martin javier.mar
From: Javier Martin javier.mar...@vista-silicon.com
Length of H.264 headers is variable and thus it might not be
aligned for the coda to append the encoded frame. This causes
the first frame to overwrite part of the H.264 PPS.
In order to solve that, a filler NAL must be added between
From: Javier Martin javier.mar...@vista-silicon.com
Length of H.264 headers is variable and thus it might not be
aligned for the coda to append the encoded frame. This causes
the first frame to overwrite part of the H.264 PPS.
In order to solve that, a filler NAL must be added between
callbacks. (2012-09-28 13:18:23 +0200)
Javier Martin (9):
media: ov7670: add support for ov7675.
media: ov7670: make try_fmt() consistent with 'min_height' and
'min_width'.
media: ov7670: calculate framerate properly
Hi Mauro,
On 25 October 2012 18:18, Mauro Carvalho Chehab mche...@redhat.com wrote:
Em Thu, 25 Oct 2012 15:24:49 +0200
javier Martin javier.mar...@vista-silicon.com escreveu:
Hi Mauro,
do you have any problems with this series?
It didn't apply here, maybe due to its dependency from your
Hi Mauro,
On 25 October 2012 17:50, Mauro Carvalho Chehab mche...@redhat.com wrote:
Hi Javier,
Em Thu, 25 Oct 2012 15:27:08 +0200
javier Martin javier.mar...@vista-silicon.com escreveu:
Hi Mauro, Jon,
any more issues related with this series?
Patch doesn't apply anymore:
patching file
Hi Mauro,
do you have any problems with this series?
Regards.
On 29 September 2012 21:20, Jonathan Corbet cor...@lwn.net wrote:
On Thu, 27 Sep 2012 17:38:20 +0200
Javier Martin javier.mar...@vista-silicon.com wrote:
The following series includes all the changes discussed in [1] that
don't
Hi Mauro, Jon,
any more issues related with this series?
Regards.
On 29 September 2012 21:25, Jonathan Corbet cor...@lwn.net wrote:
On Fri, 28 Sep 2012 13:26:39 +0200
Javier Martin javier.mar...@vista-silicon.com wrote:
The following series migrate ov7670 sensor and current users to ctrl
. Does this
mean, that this your patch is for i.MX25? But you're saying it's for
i.MX27. Confused...
I provide this mx27 clock in the first patch of the series:
http://patchwork.linuxtv.org/patch/14915/
Yes, I made the same mistake.
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C
!
--
tejun
Thanks Fabio.
Acked-by: Javier Martin javier.mar...@vista-silicon.com
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942 25 32 60
www.vista-silicon.com
--
To unsubscribe from this list: send the line
-imx27.c;h=3b6b640eed247ea1b7848c7a7fa01801f0190cde;hb=b066f61482c7eac44e656499426a3c56d29c32ed#l226
Regards.
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942 25 32 60
www.vista-silicon.com
--
To unsubscribe from
823a
mx2-camera mx2-camera.0: MX2 Camera (CSI) driver probed, clock frequency:
4433
Tested-by: Gaëtan Carlier gcem...@gmail.com
Sorry I missed patch 1/2. Both patches are correct:
Tested-by: Javier Martin javier.mar...@vista-silicon.com
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE
-usb2-udc);
--
1.7.9.5
Tested-by: Javier Martin javier.mar...@vista-silicon.com
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942 25 32 60
www.vista-silicon.com
--
To unsubscribe from this list: send the line
On 6 October 2012 17:19, Mauro Carvalho Chehab mche...@infradead.org wrote:
Em Thu, 27 Sep 2012 08:58:33 +0200
javier Martin javier.mar...@vista-silicon.com escreveu:
Hi Jonathan,
thank you for your time.
On 26 September 2012 18:40, Jonathan Corbet cor...@lwn.net wrote:
This is going
.
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942 25 32 60
www.vista-silicon.com
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More
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
Signed-off-by: Hans Verkuil hverk...@xs4all.nl
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
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
And added a missing kfree to clean up the via_camera struct.
Signed-off-by: Hans Verkuil hverk...@xs4all.nl
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media/platform/via-camera.c | 60 ---
1 file changed, 14 insertions(+), 46
Signed-off-by: Hans Verkuil hverk...@xs4all.nl
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media/i2c/ov7670.c | 295 +---
1 file changed, 115 insertions(+), 180 deletions(-)
diff --git a/drivers/media/i2c/ov7670.c b/drivers
Hi Hans,
On 28 September 2012 10:23, Hans Verkuil hverk...@xs4all.nl 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
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
Signed-off-by: Hans Verkuil hverk...@xs4all.nl
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
Changes since v1:
- Use v4l2_ctrl_auto_cluster() for auto_gain and auto_exp.
---
drivers/media/i2c/ov7670.c | 310
1 file changed, 112
Signed-off-by: Hans Verkuil hverk...@xs4all.nl
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
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
And added a missing kfree to clean up the via_camera struct.
Signed-off-by: Hans Verkuil hverk...@xs4all.nl
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media/platform/via-camera.c | 60 ---
1 file changed, 14 insertions(+), 46
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 javier.mar...@vista-silicon.com
---
drivers/media/i2c/ov7670.c |7 ---
1
Hi Hans,
On 28 September 2012 13:05, Hans Verkuil hverk...@xs4all.nl wrote:
On Fri September 28 2012 12:50:55 Javier Martin wrote:
Signed-off-by: Hans Verkuil hverk...@xs4all.nl
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
Changes since v1:
- Use v4l2_ctrl_auto_cluster
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
Reviewed-by: Hans Verkuil hans.verk...@cisco.com
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
Changes since v2:
- Do not use 'cur.val' to get gain value.
---
drivers/media/i2c/ov7670.c | 310
1 file changed, 112 insertions
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 hans.verk...@cisco.com
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
And added a missing kfree to clean up the via_camera struct.
Reviewed-by: Hans Verkuil hans.verk...@cisco.com
Signed-off-by: Hans Verkuil hverk...@xs4all.nl
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media/platform/via-camera.c | 60
Reviewed-by: Hans Verkuil hans.verk...@cisco.com
Signed-off-by: Hans Verkuil hverk...@xs4all.nl
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media/platform/marvell-ccic/mcam-core.c | 54 ---
drivers/media/platform/marvell-ccic/mcam-core.h |2
Hi Jonathan,
thank you for your time.
On 26 September 2012 18:40, Jonathan Corbet cor...@lwn.net wrote:
This is going to have to be quick, sorry...
On Wed, 26 Sep 2012 11:47:53 +0200
Javier Martin javier.mar...@vista-silicon.com wrote:
+static struct ov7670_win_size ov7670_win_sizes[2][4
On 26 September 2012 18:42, Jonathan Corbet cor...@lwn.net wrote:
On Wed, 26 Sep 2012 11:47:54 +0200
Javier Martin javier.mar...@vista-silicon.com wrote:
'min_height' and 'min_width' are variables that allow to specify the minimum
resolution that the sensor will achieve. This patch make v4l2
On 26 September 2012 18:50, Jonathan Corbet cor...@lwn.net wrote:
On Wed, 26 Sep 2012 11:47:55 +0200
Javier Martin javier.mar...@vista-silicon.com wrote:
According to the datasheet ov7675 uses a formula to achieve
the desired framerate that is different from the operations
done
On 26 September 2012 18:52, Jonathan Corbet cor...@lwn.net wrote:
On Wed, 26 Sep 2012 11:47:56 +0200
Javier Martin javier.mar...@vista-silicon.com wrote:
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
This one needs a changelog - what does bypassing the PLL do and why might
On 26 September 2012 18:52, Jonathan Corbet cor...@lwn.net wrote:
On Wed, 26 Sep 2012 11:47:57 +0200
Javier Martin javier.mar...@vista-silicon.com wrote:
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media/i2c/ov7670.c |8
include/media/ov7670.h
The following series includes all the changes discussed in [1] that
don't affect either bridge drivers that use ov7670 or soc-camera framework
For this reason they are considered non controversial and sent separately.
At least 1 more series will follow in order to implement all features
described
ov7675 and ov7670 share the same registers but there is no way
to distinguish them at runtime. However, they require different
tweaks to achieve the desired resolution. For this reason this
patch adds a new ov7675 entry to the ov7670_id table.
Signed-off-by: Javier Martin javier.mar...@vista
will be used for ov7675 only.
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
Changes since v1:
- Create separate functions for frame rate control.
---
drivers/media/i2c/ov7670.c | 136 ++--
1 file changed, 118 insertions(+), 18 deletions
'min_height' and 'min_width' are variables that allow to specify the minimum
resolution that the sensor will achieve. This patch make v4l2 fmt callbacks
consider this parameters in order to return valid data to user space.
Acked-by: Jonathan Corbet cor...@lwn.net
Signed-off-by: Javier Martin
-off-by: Javier Martin javier.mar...@vista-silicon.com
---
Changes since v1:
- Added changelog.
---
drivers/media/i2c/ov7670.c | 28 ++--
include/media/ov7670.h |1 +
2 files changed, 27 insertions(+), 2 deletions(-)
diff --git a/drivers/media/i2c/ov7670.c b
Some bridge drivers captures pixels during blanking periods if
pixclk is enabled. In order to avoid capturing bogus data we need to
disable pixclk in the sensor during those blanking periods.
Acked-by: Jonathan Corbet cor...@lwn.net
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
The following series includes all the changes discussed in [1] that
don't affect either bridge drivers that use ov7670 or soc-camera framework
For this reason they are considered non controversial and sent separately.
At least 1 more series will follow in order to implement all features
described
ov7675 and ov7670 share the same registers but there is no way
to distinguish them at runtime. However, they require different
tweaks to achieve the desired resolution. For this reason this
patch adds a new ov7675 entry to the ov7670_id table.
Signed-off-by: Javier Martin javier.mar...@vista
'min_height' and 'min_width' are variables that allow to specify the minimum
resolution that the sensor will achieve. This patch make v4l2 fmt callbacks
consider this parameters in order to return valid data to user space.
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media/i2c/ov7670.c | 24 ++--
include/media/ov7670.h |1 +
2 files changed, 23 insertions(+), 2 deletions(-)
diff --git a/drivers/media/i2c/ov7670.c b/drivers/media/i2c/ov7670.c
index 175fbfc
will be used for ov7675 only.
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media/i2c/ov7670.c | 122 ++--
1 file changed, 105 insertions(+), 17 deletions(-)
diff --git a/drivers/media/i2c/ov7670.c b/drivers/media/i2c/ov7670.c
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media/i2c/ov7670.c |8
include/media/ov7670.h |1 +
2 files changed, 9 insertions(+)
diff --git a/drivers/media/i2c/ov7670.c b/drivers/media/i2c/ov7670.c
index 54fb535..f7e4341 100644
--- a/drivers
On 26 September 2012 11:47, Javier Martin
javier.mar...@vista-silicon.com wrote:
The following series includes all the changes discussed in [1] that
don't affect either bridge drivers that use ov7670 or soc-camera framework
For this reason they are considered non controversial and sent
:
http://comments.gmane.org/gmane.linux.drivers.video-input-infrastructure/53627
The pull request is a way to tell Mauro this is ready to be merged in
his linux-media tree and making things easier for him.
Regards.
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los
On 20 September 2012 10:03, Richard Zhao richard.z...@freescale.com wrote:
On Thu, Sep 20, 2012 at 09:10:46AM +0200, javier Martin wrote:
Hi Richard,
On 20 September 2012 05:32, Richard Zhao richard.z...@freescale.com wrote:
why is it a request-pull?
After 5 version of Philipp's patches we
Hi Shawn,
On 18 September 2012 09:43, Shawn Guo shawn@linaro.org wrote:
On Mon, Sep 17, 2012 at 03:36:07PM +0200, javier Martin wrote:
This patch breaks the driver:
Javier,
Can you please apply the following change to see if it fixes the
problem?
Shawn
@@ -1783,6 +1783,8 @@ static
On 17 September 2012 15:59, Guennadi Liakhovetski g.liakhovet...@gmx.de wrote:
On Mon, 17 Sep 2012, javier Martin wrote:
Hi Shawn,
On 17 September 2012 11:21, Guennadi Liakhovetski g.liakhovet...@gmx.de
wrote:
On Mon, 17 Sep 2012, Shawn Guo wrote:
It changes the driver to use
1 - 100 of 447 matches
Mail list logo
