[PATCH 2/2 v2] Fix capture issues for non 8-bit per pixel formats

2011-01-17 Thread Alberto Panizzo
verse. Signed-off-by: Alberto Panizzo --- drivers/media/video/mx3_camera.c | 64 + 1 files changed, 50 insertions(+), 14 deletions(-) diff --git a/drivers/media/video/mx3_camera.c b/drivers/media/video/mx3_camera.c index b9cb4a4..9391006 100644 --- a/drivers/media/

Re: [PATCH 2/2] Fix capture issues for non 8-bit per pixel formats

2011-01-17 Thread Alberto Panizzo
On Sat, 2011-01-15 at 22:35 +0100, Guennadi Liakhovetski wrote: > On Wed, 12 Jan 2011, Alberto Panizzo wrote: > > > If the camera was set to output formats like RGB565 YUYV or SBGGR10, > > the resulting image was scrambled due to erroneous interpretations of > > hori

[PATCH 2/2] Fix capture issues for non 8-bit per pixel formats

2011-01-12 Thread Alberto Panizzo
. In the end in mx3_camera_get_formats, is fixed an erroneous debug message that try to shows info from an invalid xlate pointer. Signed-off-by: Alberto Panizzo --- drivers/media/video/mx3_camera.c | 66 + 1 files changed, 51 insertions(+), 15 deletions(-)

[PATCH 1/2] soc_mediabus: export a useful method to obtain the number of samples that makes up a pixel format

2011-01-12 Thread Alberto Panizzo
Signed-off-by: Alberto Panizzo --- drivers/media/video/soc_mediabus.c | 14 ++ include/media/soc_mediabus.h |1 + 2 files changed, 15 insertions(+), 0 deletions(-) diff --git a/drivers/media/video/soc_mediabus.c b/drivers/media/video/soc_mediabus.c index 9139121

[PATCH 0/2] Fix the way mx3_camera manage non 8-bpp pixel formats

2011-01-12 Thread Alberto Panizzo
This patch series enable the mx3_camera driver to manage correctly pixel formats like RGB565 UYVY and SBGGR10 This patch series applies to the staging/for_2.6.38-rc1 and I hope it will reach the mainline in one of the .38-rcN Best regards, Alberto! -- To unsubscribe from this list: send the line

Re: [PATCH 2/3] mx3_camera: Support correctly the YUV222 and BAYER configurations of CSI

2011-01-11 Thread Alberto Panizzo
On Mon, 2011-01-03 at 23:07 +0100, Alberto Panizzo wrote: > On Mon, 2011-01-03 at 20:37 +0100, Guennadi Liakhovetski wrote: > > On Mon, 3 Jan 2011, Alberto Panizzo wrote: > > > > > On Thu, 2010-12-30 at 20:38 +0100, Guennadi Liakhovetski wrote: > > > > On Sat

Re: [PATCH 2/3] mx3_camera: Support correctly the YUV222 and BAYER configurations of CSI

2011-01-03 Thread Alberto Panizzo
On Mon, 2011-01-03 at 20:37 +0100, Guennadi Liakhovetski wrote: > On Mon, 3 Jan 2011, Alberto Panizzo wrote: > > > On Thu, 2010-12-30 at 20:38 +0100, Guennadi Liakhovetski wrote: > > > On Sat, 18 Dec 2010, Guennadi Liakhovetski wrote: > > > > > > > Albe

Re: [PATCH 2/3] mx3_camera: Support correctly the YUV222 and BAYER configurations of CSI

2011-01-03 Thread Alberto Panizzo
rgb565. Supporting the CSI-YUV422 is a plus only to show how the CSI works. Best Regards, Alberto! > Thanks > Guennadi > > > On Wed, 1 Dec 2010, Guennadi Liakhovetski wrote: > > > > > On Sun, 28 Nov 2010, Alberto Panizzo wrote: > > > > > &

Re: [PATCH 2/3] mx3_camera: Support correctly the YUV222 and BAYER configurations of CSI

2011-01-03 Thread Alberto Panizzo
On Wed, 2010-12-01 at 19:54 +0100, Guennadi Liakhovetski wrote: > On Sun, 28 Nov 2010, Alberto Panizzo wrote: > > > This patch is tested and works with the OV2640 camera that output > > YUV422 (UYVY) and RGB565 data. > > > > The YUV422 format is managed to be co

Re: [PATCH 2/3] mx3_camera: Support correctly the YUV222 and BAYER configurations of CSI

2011-01-03 Thread Alberto Panizzo
'll go deeper on your suggestions in these days and hope to find a good solution. Thank you, Alberto! > > > On Wed, 1 Dec 2010, Guennadi Liakhovetski wrote: > > > > > On Sun, 28 Nov 2010, Alberto Panizzo wrote: > > > > > > > This patch is tested

[PATCH v2] V4L2: Add a v4l2-subdev (soc-camera) driver for OmniVision OV2640 sensor

2010-12-02 Thread Alberto Panizzo
Signed-off-by: Alberto Panizzo --- v2 changes: - Fixed addressed errors. - Added trivial .cropcap and .g_crop functions based on the whole size of sensor. drivers/media/video/Kconfig |6 + drivers/media/video/Makefile|1 + drivers/media/video/ov2640.c| 1205

[PATCH v3] soc_camera: Add the ability to bind regulators to soc_camedra devices

2010-12-02 Thread Alberto Panizzo
In certain machines, camera devices are supplied directly by a number of regulators. This patch add the ability to drive these regulators directly by the soc_camera driver. Signed-off-by: Alberto Panizzo --- v2 changes: It is used the more standard regulator_bulk API, thanks to Mark Brown for

Re: [PATCH 3/3] V4L2: Add a v4l2-subdev (soc-camera) driver for OmniVision OV2640 sensor

2010-12-02 Thread Alberto Panizzo
ollowed an old suggestion to add all that is showed by the get_maintainer script. That is not always sane at this point. > > In general looks good, just a couple of easy to fix remarks below, and, > please, fix line wrapping with the next version. > > On Sun, 28 Nov 2010, Alberto

Re: [PATCH v2] soc_camera: Add the ability to bind regulators to soc_camedra devices

2010-12-01 Thread Alberto Panizzo
On mer, 2010-12-01 at 18:26 +0100, Guennadi Liakhovetski wrote: > On Tue, 30 Nov 2010, Alberto Panizzo wrote: > > > In certain machines, camera devices are supplied directly > > by a number of regulators. This patch add the ability to drive > > these regulators directly

[PATCH v2] soc_camera: Add the ability to bind regulators to soc_camedra devices

2010-11-30 Thread Alberto Panizzo
In certain machines, camera devices are supplied directly by a number of regulators. This patch add the ability to drive these regulators directly by the soc_camera driver. Signed-off-by: Alberto Panizzo --- v2 changes: It is used the more standard regulator_bulk API, thanks to Mark Brown for

Re: [PATCH 2/3] mx3_camera: Support correctly the YUV222 and BAYER configurations of CSI

2010-11-30 Thread Alberto Panizzo
On mar, 2010-11-30 at 15:31 +0100, Guennadi Liakhovetski wrote: > On Tue, 30 Nov 2010, Alberto Panizzo wrote: > > > On dom, 2010-11-28 at 18:24 +0100, Alberto Panizzo wrote: > > > This patch is tested and works with the OV2640 camera that output > > >

Re: [PATCH 2/3] mx3_camera: Support correctly the YUV222 and BAYER configurations of CSI

2010-11-30 Thread Alberto Panizzo
On dom, 2010-11-28 at 18:24 +0100, Alberto Panizzo wrote: > This patch is tested and works with the OV2640 camera that output > YUV422 (UYVY) and RGB565 data. > > The YUV422 format is managed to be converted in IPU internal YUV444 format > so this stream could be used in the

Re: [PATCH 1/3] soc_camera: Add the ability to bind regulators to soc_camedra devices

2010-11-30 Thread Alberto Panizzo
On lun, 2010-11-29 at 15:51 +, Mark Brown wrote: > On Mon, Nov 29, 2010 at 10:34:57AM +0100, Alberto Panizzo wrote: > > On dom, 2010-11-28 at 20:05 +0100, Guennadi Liakhovetski wrote: > > > > (2) would anyone really want to > > > use several regulators for a c

Re: [PATCH 1/3] soc_camera: Add the ability to bind regulators to soc_camedra devices

2010-11-29 Thread Alberto Panizzo
Hi Guennadi, On dom, 2010-11-28 at 20:05 +0100, Guennadi Liakhovetski wrote: > On Sun, 28 Nov 2010, Alberto Panizzo wrote: > > > In certain machines, camera devices are supplied directly > > by a number of regulators. This patch add the ability to drive > > these re

[PATCH 3/3] V4L2: Add a v4l2-subdev (soc-camera) driver for OmniVision OV2640 sensor

2010-11-28 Thread Alberto Panizzo
Signed-off-by: Alberto Panizzo --- drivers/media/video/Kconfig |6 + drivers/media/video/Makefile|1 + drivers/media/video/ov2640.c| 1153 +++ include/media/v4l2-chip-ident.h |1 + 4 files changed, 1161 insertions(+), 0 deletions

Re: [PATCH 2/3] mx3_camera: Support correctly the YUV222 and BAYER configurations of CSI

2010-11-28 Thread Alberto Panizzo
be moved only from CSI to memory. Signed-off-by: Alberto Panizzo --- Before applying, please give me feedback if this break in some way other pixel formats! drivers/media/video/mx3_camera.c | 126 +- 1 files changed, 110 insertions(+), 16 deletions

[PATCH 1/3] soc_camera: Add the ability to bind regulators to soc_camedra devices

2010-11-28 Thread Alberto Panizzo
sual with the platform device description: static struct platform_device machine_my_camera = { .name = "soc-camera-pdrv", .id = 0, .dev= { .platform_data = &iclink_my_camera, }, }; Signed-off-b