Re: OMAP3 Multiple camera support
Hi Laurent, What you are essentially saying is CSI2A = Smart Sensor (YUV422) CSI2C = Sensor that gives out RAW Bayer. I guess this is a driver limitation? Am i correct? Also, Can i have something like this? SMART Sensor = CSI2A = H3A = MEM (Can i have this) CSI2C = ISP = H3A = MEM Can't i have H3A for both the pipelines? Or Can i enable H3A on the fly for both the sensors? One After the other? Regards, Sriram On Thu, Sep 18, 2014 at 1:55 PM, Laurent Pinchart laurent.pinch...@ideasonboard.com wrote: Hi Sriram, On Wednesday 17 September 2014 23:06:42 Sriram V wrote: Hi Does OMAP3 camera driver support multiple cameras at the same time. As i understand - You can have simultaneous YUV422 (Directly to memory) and another one passing through camera controller ISP? I Also, wanted to check if anyone has tried having multiple cameras on omap3 with the existing driver. The driver does support capturing from multiple cameras at the same time, provided one of them is connected to the CSI2A receiver. You can then capture raw frames from the CSI2A receiver output while processing frames from the other camera (connected to CSI1/CCP2, CSI2C or parallel interface) using the whole ISP pipeline. Please note that the consumer OMAP3 variants are documented by TI as not including the CSI receivers. However, several developers have reported that the receivers are present and usable at least in some of the chips. -- Regards, Laurent Pinchart -- Regards, Sriram -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
OMAP3 Multiple camera support
Hi Does OMAP3 camera driver support multiple cameras at the same time. As i understand - You can have simultaneous YUV422 (Directly to memory) and another one passing through camera controller ISP? I Also, wanted to check if anyone has tried having multiple cameras on omap3 with the existing driver. -- Regards, Sriram -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
H3A module on omap4 iss
Hi, I am planning to work on getting the H3A support (Auto White balance, Auto Exposure and Auto Focus Support) for OMAP4 ISS. I wanted to check if anyone is working to get this module working. Is OMAP3 H3A similar or same as OMAP4 H3A. Can i make use of the OMAP3 code base for h3a or how complex is this activity? Also, i wanted to how how to test the v4l resizer driver in omap4iss? Any help is highly appreciated. -- Regards, Sriram -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: H3A module on omap4 iss
Thanks for your response. Going through the Datasheet omap3isp code. what i understand is The code enables the H3A engine for AF, AE and AWB. Now, the H3A produces co-efficients which need to be used for achieving actual AF, AE AWB. Now, I could not find any references where these co-efficents are used to do AF, AE AWB. My specific question is now if i need to do AF - Do you know any formula or algorithm which can make use of these co-coefficients and control the sensor motor. Similarly - How AWB is done with the help of these co-efficients when AWB is enabled? Correct me if i am wrong. Thanks. On Wed, Aug 20, 2014 at 8:02 PM, Laurent Pinchart laurent.pinch...@ideasonboard.com wrote: Hi Sriram, On Wednesday 20 August 2014 11:55:12 Sriram V wrote: Hi, I am planning to work on getting the H3A support (Auto White balance, Auto Exposure and Auto Focus Support) for OMAP4 ISS. That would be great ! I wanted to check if anyone is working to get this module working. Not to my knowledge. I'm not (at least for now, but I could need H3A support at some point in the future). Is OMAP3 H3A similar or same as OMAP4 H3A. Can i make use of the OMAP3 code base for h3a or how complex is this activity? The AF and AE engines look pretty similar indeed. It would be nice if the OMAP3 ISP AF and AE code could be shared with the OMAP4 ISS driver. That would require some refactoring though. One thing we're missing is standardization of H3A APIs in V4L2, I'd like to see that happen. Also, i wanted to how how to test the v4l resizer driver in omap4iss? Here's the full pipeline configuration I use. Please note that the OMAP4 ISS resizer implementation doesn't support resizing yet, it just hardcodes the resizer ratio to 1:1. IFMT=SBGGR10 ISIZE=1920x1084 OFMT=UYVY OSIZE=1920x1080 CFMT=YUYV1_5X8 media-ctl -l 'OMAP4 ISS CSI2a:1 - OMAP4 ISS ISP IPIPEIF:0 [1]' media-ctl -l 'OMAP4 ISS ISP IPIPEIF:2 - OMAP4 ISS ISP IPIPE:0 [1]' media-ctl -l 'OMAP4 ISS ISP IPIPE:1 - OMAP4 ISS ISP resizer:0 [1]' media-ctl -l 'OMAP4 ISS ISP resizer:1 - OMAP4 ISS ISP resizer a output:0 [1]' media-ctl -V \sensor\:0 [fmt:$IFMT/$ISIZE] media-ctl -V \OMAP4 ISS CSI2a\:1 [fmt:$IFMT/$ISIZE] media-ctl -V \OMAP4 ISS ISP IPIPEIF\:0 [fmt:$IFMT/$ISIZE] media-ctl -V \OMAP4 ISS ISP IPIPE\:0 [fmt:$IFMT/$ISIZE] media-ctl -V \OMAP4 ISS ISP IPIPE\:1 [fmt:$OFMT/$OSIZE] media-ctl -V \OMAP4 ISS ISP resizer\:0 [fmt:$OFMT/$OSIZE] media-ctl -V \OMAP4 ISS ISP resizer\:1 [fmt:$CFMT/$OSIZE] -- Regards, Laurent Pinchart -- Regards, Sriram -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Android Support for camera?
Hi Sergio, I understand that you are working on providing Android HAL Support for camera on omap4. Were you able to capture and record? -- Regards, Sriram -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Video Capture Issue
Hi Aguirre Sergio,
1) Looks like it could be a data lane issue. OMAP detects lots of
ERRSOTSYNCHS errors
on the datalanes (CSI2_COMPLEXIO_IRQSTATUS)
2) Even if i configure it to use only one data lane on both sides. It detects
errors on other data lanes.
That explains the abnormally high number of these error interrupts and a
frame completion interrupt once in a while.
I guess, I need to check my configuration settings.
Thanks,
Sriram
On Tue, Feb 28, 2012 at 9:12 PM, Aguirre, Sergio saagui...@ti.com wrote:
Hi Sriram,
On Tue, Feb 28, 2012 at 8:46 AM, Sriram V vshrir...@gmail.com wrote:
Hi Aguirre Sergio,
On Tue, Feb 28, 2012 at 9:08 AM, Aguirre, Sergio saagui...@ti.com wrote:
Sriram,
On Sun, Feb 26, 2012 at 8:54 AM, Sriram V vshrir...@gmail.com wrote:
Hi,
When I take the dump of the buffer which is pointed by DATA MEM
PING ADDRESS. It always shows 0x55.
Even if i write 0x00 to the address. I do notice that it quickly
changes to 0x55.
Under what conditions could this happen? What am i missing here.
If you're using yavta for capture, notice that it clears out the
buffers before queuing them in:
static int video_queue_buffer(struct device *dev, int index, enum
buffer_fill_mode fill)
{
struct v4l2_buffer buf;
int ret;
...
...
if (dev-type == V4L2_BUF_TYPE_VIDEO_OUTPUT) {
...
} else {
if (fill BUFFER_FILL_FRAME)
memset(dev-buffers[buf.index].mem, 0x55,
dev-buffers[index].size);
if (fill BUFFER_FILL_PADDING)
memset(dev-buffers[buf.index].mem +
dev-buffers[index].size,
0x55, dev-buffers[index].padding);
}
...
}
So, just make sure this condition is not met.
Unfortunately, this condition is met. For some reason, ISS thinks
it has got valid frame. Whereas the Image data is not populated into
the buffers.
The register CSI2_CTX_CTRL1_i[COUNT] keeps getting toggled between 0 and 1
indicating a frame arrival.
I also notice that on some frames, The first 0x200 bytes contains data
other than 0x55
and the rest are 0x55.
Probably this could be related to resolution settings or hsync and
vsync settings.
Probably, my chip configuration is faulty.
Hmm, sounds like it.
Can you try adding this to the top of the file?
#define DEBUG
So that the dev_dbg() prints get executed?
I'm curious to see if you detect any ComplexIO errors on
omap4iss_csi2_isr()...
I do notice that the OMAP4 ISS is tested to work with OV5640 (YUV422
Frames) and OV5650 (Raw Data)
When you say 422 Frames only. Do you mean 422-8Bit Mode?.
Yes. When saving YUV422 to memory, you can only use this mode AFAIK.
I havent tried RAW12 which my device gives, Do i have to update only
the Data Format Selection register
of the ISS for RAW12?
Ok, now it makes sense.
So, if your CSI2 source is giving, you need to make sure:
CSI2_CTX_CTRL2_0.FORMAT[9:0] is:
- 0xAC: RAW12 + EXP16
or
- 0x2C: RAW12
The difference is that the EXP16 variant, will save to memory in
expansion to 2 bytes, instead of 12 bits, so it'll be byte aligned.
Can you try attached patch?
With RAW12 configuration, I dont see any interrupts at all.
Ok,
Then this means your CSI2 transmitter (sensor) is actually sending
YUV422, and not RAW12.
Nevermind that patch then...
Regards,
Sergio
Regards,
Sergio
Please advice.
On Thu, Feb 23, 2012 at 11:24 PM, Sriram V vshrir...@gmail.com wrote:
Hi,
1) An Hexdump of the captured file shows 0x55 at all locations.
Is there any buffer location i need to check.
2) I have tried with devel branch.
3) Changing the polarities doesnt help either.
4) The sensor is giving out YUV422 8Bit Mode,
Will 0x52001074 = 0x0A1E (UYVY Format) it bypass the ISP
and dump directly into memory.
On 2/23/12, Aguirre, Sergio saagui...@ti.com wrote:
Hi Sriram,
On Thu, Feb 23, 2012 at 11:25 AM, Sriram V vshrir...@gmail.com wrote:
Hi,
1) I am trying to get a HDMI to CSI Bridge chip working with OMAP4 ISS.
The issue is the captured frames are completely green in color.
Sounds like the buffer is all zeroes, can you confirm?
2) The Chip is configured to output VGA Color bar sequence with
YUV422-8Bit and
uses datalane 0 only.
3) The Format on OMAP4 ISS is UYVY (Register 0x52001074 = 0x0A1E)
I am trying to directly dump the data into memory without ISP
processing.
Please advice.
Just to be clear on your environment, which branch/commitID are you based
on?
Regards,
Sergio
--
Regards,
Sriram
--
To unsubscribe from this list: send the line unsubscribe linux-media
in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Regards,
Sriram
--
Regards,
Sriram
--
Regards,
Sriram
--
Regards,
Sriram
--
To unsubscribe
Re: Video Capture Issue
Hi, When I take the dump of the buffer which is pointed by DATA MEM PING ADDRESS. It always shows 0x55. Even if i write 0x00 to the address. I do notice that it quickly changes to 0x55. Under what conditions could this happen? What am i missing here. I do notice that the OMAP4 ISS is tested to work with OV5640 (YUV422 Frames) and OV5650 (Raw Data) When you say 422 Frames only. Do you mean 422-8Bit Mode?. I havent tried RAW12 which my device gives, Do i have to update only the Data Format Selection register of the ISS for RAW12? Please advice. On Thu, Feb 23, 2012 at 11:24 PM, Sriram V vshrir...@gmail.com wrote: Hi, 1) An Hexdump of the captured file shows 0x55 at all locations. Is there any buffer location i need to check. 2) I have tried with devel branch. 3) Changing the polarities doesnt help either. 4) The sensor is giving out YUV422 8Bit Mode, Will 0x52001074 = 0x0A1E (UYVY Format) it bypass the ISP and dump directly into memory. On 2/23/12, Aguirre, Sergio saagui...@ti.com wrote: Hi Sriram, On Thu, Feb 23, 2012 at 11:25 AM, Sriram V vshrir...@gmail.com wrote: Hi, 1) I am trying to get a HDMI to CSI Bridge chip working with OMAP4 ISS. The issue is the captured frames are completely green in color. Sounds like the buffer is all zeroes, can you confirm? 2) The Chip is configured to output VGA Color bar sequence with YUV422-8Bit and uses datalane 0 only. 3) The Format on OMAP4 ISS is UYVY (Register 0x52001074 = 0x0A1E) I am trying to directly dump the data into memory without ISP processing. Please advice. Just to be clear on your environment, which branch/commitID are you based on? Regards, Sergio -- Regards, Sriram -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Regards, Sriram -- Regards, Sriram -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Video Capture Issue
Hi, 1) I am trying to get a HDMI to CSI Bridge chip working with OMAP4 ISS. The issue is the captured frames are completely green in color. 2) The Chip is configured to output VGA Color bar sequence with YUV422-8Bit and uses datalane 0 only. 3) The Format on OMAP4 ISS is UYVY (Register 0x52001074 = 0x0A1E) I am trying to directly dump the data into memory without ISP processing. Please advice. -- Regards, Sriram -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Video Capture Issue
Hi, 1) An Hexdump of the captured file shows 0x55 at all locations. Is there any buffer location i need to check. 2) I have tried with devel branch. 3) Changing the polarities doesnt help either. 4) The sensor is giving out YUV422 8Bit Mode, Will 0x52001074 = 0x0A1E (UYVY Format) it bypass the ISP and dump directly into memory. On 2/23/12, Aguirre, Sergio saagui...@ti.com wrote: Hi Sriram, On Thu, Feb 23, 2012 at 11:25 AM, Sriram V vshrir...@gmail.com wrote: Hi, 1) I am trying to get a HDMI to CSI Bridge chip working with OMAP4 ISS. The issue is the captured frames are completely green in color. Sounds like the buffer is all zeroes, can you confirm? 2) The Chip is configured to output VGA Color bar sequence with YUV422-8Bit and uses datalane 0 only. 3) The Format on OMAP4 ISS is UYVY (Register 0x52001074 = 0x0A1E) I am trying to directly dump the data into memory without ISP processing. Please advice. Just to be clear on your environment, which branch/commitID are you based on? Regards, Sergio -- Regards, Sriram -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Regards, Sriram -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
omap3isp driver
Hi, Does the omap3isp driver implementation support rgb888 format? Regards, sriram -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Camera Support
Hi, OMAP3 ISP Supports 2 camera ports (csi and parallel) Does the existing ISP drivers support both of them at the same time. Regards, sriram -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [REVIEW PATCH 2/2] Added OMAP3EVM Multi-Media Daughter Card Support
Hi Vaibav, I am using Sergio's patch that was posted on dec12th. I have been trying to apply the mdc driver patches + camera drivers/isp drivers patches related to mdc on sergio's dec 12th patches. They fail to apply at all. I would appreciate if you could send me those patches. Regards, sriram On Wed, Jan 7, 2009 at 11:37 AM, hvaib...@ti.com wrote: From: Vaibhav Hiremath hvaib...@ti.com This is first version of OMAP3EVM Mulit-Media Daughter Card support. Tested: - TVP5146 (BT656) decoder interface on top of Sergio's ISP-Camera patches. - Loopback application, capturing image through TVP5146 and displaying it onto the TV/LCD on top of Hardik's V4L2 driver. - Basic functionality of HSUSB Transceiver USB-83320 - TODO: - Camera sensor support - Driver header file inclusion (dependency on ISP-Camera patches) - Some more clean-up may required. Signed-off-by: Brijesh Jadav brijes...@ti.com Signed-off-by: Hardik Shah hardik.s...@ti.com Signed-off-by: Manjunath Hadli m...@ti.com Signed-off-by: R Sivaraj siva...@ti.com Signed-off-by: Vaibhav Hiremath hvaib...@ti.com --- arch/arm/mach-omap2/Kconfig | 4 + arch/arm/mach-omap2/Makefile | 1 + arch/arm/mach-omap2/board-omap3evm-dc.c | 417 +++ arch/arm/mach-omap2/board-omap3evm-dc.h | 43 arch/arm/mach-omap2/mux.c | 7 + arch/arm/plat-omap/include/mach/mux.h | 4 + 6 files changed, 476 insertions(+), 0 deletions(-) mode change 100644 = 100755 arch/arm/mach-omap2/Kconfig mode change 100644 = 100755 arch/arm/mach-omap2/Makefile create mode 100755 arch/arm/mach-omap2/board-omap3evm-dc.c create mode 100755 arch/arm/mach-omap2/board-omap3evm-dc.h mode change 100644 = 100755 arch/arm/mach-omap2/mux.c mode change 100644 = 100755 arch/arm/plat-omap/include/mach/mux.h diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig old mode 100644 new mode 100755 index ca24a7a..094c97f --- a/arch/arm/mach-omap2/Kconfig +++ b/arch/arm/mach-omap2/Kconfig @@ -121,6 +121,10 @@ config MACH_OMAP3EVM bool OMAP 3530 EVM board depends on ARCH_OMAP3 ARCH_OMAP34XX +config MACH_OMAP3EVM_DC + bool OMAP 3530 EVM daughter card board + depends on ARCH_OMAP3 ARCH_OMAP34XX MACH_OMAP3EVM + config MACH_OMAP3_BEAGLE bool OMAP3 BEAGLE board depends on ARCH_OMAP3 ARCH_OMAP34XX diff --git a/arch/arm/mach-omap2/Makefile b/arch/arm/mach-omap2/Makefile old mode 100644 new mode 100755 index 3897347..16fa35a --- a/arch/arm/mach-omap2/Makefile +++ b/arch/arm/mach-omap2/Makefile @@ -60,6 +60,7 @@ obj-$(CONFIG_MACH_OMAP3EVM) += board-omap3evm.o \ usb-musb.o usb-ehci.o \ board-omap3evm-flash.o \ twl4030-generic-scripts.o +obj-$(CONFIG_MACH_OMAP3EVM_DC) += board-omap3evm-dc.o obj-$(CONFIG_MACH_OMAP3_BEAGLE) += board-omap3beagle.o \ usb-musb.o usb-ehci.o \ mmc-twl4030.o \ diff --git a/arch/arm/mach-omap2/board-omap3evm-dc.c b/arch/arm/mach-omap2/board-omap3evm-dc.c new file mode 100755 index 000..233c219 --- /dev/null +++ b/arch/arm/mach-omap2/board-omap3evm-dc.c @@ -0,0 +1,417 @@ +/* + * arch/arm/mach-omap2/board-omap3evm-dc.c + * + * Driver for OMAP3 EVM Daughter Card + * + * Copyright (C) 2008 Texas Instruments Inc + * Author: Vaibhav Hiremath hvaib...@ti.com + * + * Contributors: + * Anuj Aggarwal anuj.aggar...@ti.com + * Sivaraj R siva...@ti.com + * + * This package is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + * + * You should have received a copy of the GNU General Public License + * along with this program; if not, write to the Free Software + * Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. + * + */ + +#include linux/module.h +#include linux/kernel_stat.h +#include linux/init.h +#include linux/i2c.h +#include linux/delay.h +#include linux/spinlock.h +#include linux/clk.h +#include linux/device.h +#include linux/io.h +#include linux/gpio.h + +#include mach/io.h +#include mach/mux.h + +#if defined(CONFIG_VIDEO_TVP514X) || defined(CONFIG_VIDEO_TVP514X_MODULE) +#include linux/videodev2.h +#include media/v4l2-int-device.h +#include media/tvp514x.h +/* include V4L2 camera driver related header file */ +#if defined(CONFIG_VIDEO_OMAP3) ||
