-kariche...@ti.com
-Original Message-
From: Hans Verkuil [mailto:hverk...@xs4all.nl]
Sent: Thursday, November 19, 2009 2:25 AM
To: Karicheri, Muralidharan
Cc: linux-media@vger.kernel.org; davinci-linux-open-
sou...@linux.davincidsp.com
Subject: Re: [PATCH v3] V4L - Adding Digital Video
Hi,
Please make this a generic driver so that it can be used across
other SoCs as well. BTW, on which SoC have you tested this driver?
There seems to be a lot of soc-camera specific stuffs here.
Example, probe() is getting a pointer to struct soc_camera_device *icd. I have
been working with
, November 19, 2009 9:55 AM
To: Karicheri, Muralidharan
Cc: Kuninori Morimoto; Linux-V4L2
Subject: RE: [PATCH] soc-camera: Add mt9t112 camera support
On Thu, 19 Nov 2009, Karicheri, Muralidharan wrote:
Hi,
Please make this a generic driver so that it can be used across
other SoCs as well. BTW
[mailto:hverk...@xs4all.nl]
Sent: Wednesday, November 18, 2009 2:33 AM
To: Mauro Carvalho Chehab
Cc: Karicheri, Muralidharan; linux-media@vger.kernel.org
Subject: Re: Help in adding documentation
On Wednesday 18 November 2009 08:24:13 Mauro Carvalho Chehab wrote:
Hans Verkuil wrote:
On Wednesday 18
Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
phone: 301-407-9583
email: m-kariche...@ti.com
-Original Message-
From: linux-media-ow...@vger.kernel.org [mailto:linux-media-
ow...@vger.kernel.org] On Behalf Of Karicheri, Muralidharan
Sent: Thursday, November 19, 2009 11:26 AM
...@ti.com
-Original Message-
From: Hans Verkuil [mailto:hverk...@xs4all.nl]
Sent: Wednesday, November 18, 2009 2:33 AM
To: Mauro Carvalho Chehab
Cc: Karicheri, Muralidharan; linux-media@vger.kernel.org
Subject: Re: Help in adding documentation
On Wednesday 18 November 2009 08:24:13 Mauro
Vaibhav,
I have some comments. I have tested this patch for normal
use case of tvp5146 capture on DM355. It looks ok. We
don't have support for power management on DM355. So I couldn't
test the suspend resume operations.
struct ccdc_hw_device {
diff --git
Mauro,
We have few patches already reviewed and ready for merge (See Hans' pull
request in the attachment. Could you merge these so that we can base our future
patches on this?
Thanks
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
email:
; Karicheri, Muralidharan; Hiremath, Vaibhav
Subject: [PATCH] VPFE Capture: Add call back function for interrupt clear
to vpfe_cfg
From: Vaibhav Hiremath hvaib...@ti.com
For the devices like AM3517, it is expected that driver clears the
interrupt in ISR. Since this is device spcific, callback function
To: linux-media@vger.kernel.org
Cc: hverk...@xs4all.nl; Karicheri, Muralidharan; Hiremath, Vaibhav
Subject: [PATCH] Davinci VPFE Capture: Add Suspend/Resume Support
From: Vaibhav Hiremath hvaib...@ti.com
Validated on AM3517 Platform.
Signed-off-by: Vaibhav Hiremath hvaib...@ti.com
---
drivers/media
: Wednesday, November 18, 2009 10:36 AM
To: Karicheri, Muralidharan; linux-media@vger.kernel.org
Cc: hverk...@xs4all.nl
Subject: RE: [PATCH] Davinci VPFE Capture: Add Suspend/Resume Support
-Original Message-
From: Karicheri, Muralidharan
Sent: Wednesday, November 18, 2009 8:55 PM
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
phone: 301-407-9583
email: m-kariche...@ti.com
-Original Message-
From: Hiremath, Vaibhav
Sent: Wednesday, November 18, 2009 11:52 AM
To: Karicheri, Muralidharan; linux-media@vger.kernel.org
Cc: hverk
I will be sending the patch for documentation today.
FYI.
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
email: m-kariche...@ti.com
-Original Message-
From: Karicheri, Muralidharan
Sent: Wednesday, November 18, 2009 12:04 PM
To: linux-media
Texas Instruments Inc.
Germantown, MD 20874
phone: 301-407-9583
email: m-kariche...@ti.com
-Original Message-
From: Mauro Carvalho Chehab [mailto:mche...@infradead.org]
Sent: Tuesday, November 17, 2009 12:58 PM
To: Karicheri, Muralidharan
Cc: Hans Verkuil; linux-media@vger.kernel.org
Subject
Message-
From: Hans Verkuil [mailto:hverk...@xs4all.nl]
Sent: Wednesday, November 18, 2009 1:09 PM
To: Karicheri, Muralidharan
Cc: linux-media@vger.kernel.org; davinci-linux-open-
sou...@linux.davincidsp.com
Subject: Re: [PATCH v2] V4L - Adding Digital Video Timings APIs
On Wednesday 18 November
Hans,
Thanks for doing the 64-bit test. I will incorporate
the below comments along with the other comments and will
post v3 of the patch with you included in the sign off.
Regards,
Murali
I did some quick 64-bit tests and discovered that we need to add the packed
attribute to struct
Carvalho Chehab [mailto:mche...@infradead.org]
Sent: Wednesday, November 18, 2009 2:48 PM
To: Karicheri, Muralidharan
Cc: Hans Verkuil; linux-media@vger.kernel.org
Subject: Re: Help in adding documentation
Karicheri, Muralidharan wrote:
Mauro,
Is there specific way to create patch
Randy,
Thanks for your comments...
Make sure that these ioctls (range) are added to/included in
Documentation/ioctl/ioctl-number.txt .
There is separate document for v4l2 APIs. These ioctls are
added to that (See my patch with similar title)
Hm, are those supposed to be small 'v' instead of
Hi Mauro,
Is there some instructions on adding new sections in the v4l2 documentation. I
had been struggling yesterday to add my documentation for video timing API. It
is easy to make minor documentation changes. But since I am adding new ioctls,
Looks like I need to create vidioc-xxx.xml
-Original Message-
From: Karicheri, Muralidharan
Sent: Tuesday, November 17, 2009 10:58 AM
To: 'Mauro Carvalho Chehab'
Cc: 'Hans Verkuil'; linux-media@vger.kernel.org
Subject: Help in adding documentation
Hi Mauro,
Is there some instructions on adding new sections in the v4l2 documentation
Mauro,
Thanks for your reply. I made progress after my email. My new file
is being processed by Makefile now. I have some issues with some
tags.
This probably means that videodev2.h has it defined, while you didn't have
Do you mean videodev2.h.xml? I see there videodev2.h under linux/include.
email: m-kariche...@ti.com
-Original Message-
From: Mauro Carvalho Chehab [mailto:mche...@infradead.org]
Sent: Tuesday, November 17, 2009 12:58 PM
To: Karicheri, Muralidharan
Cc: Hans Verkuil; linux-media@vger.kernel.org
Subject: Re: Help in adding documentation
Karicheri, Muralidharan
Hans,
Please see my response below.
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
email: m-kariche...@ti.com
I think Santiago based his driver on tvp514x which doesn't update the
register until the chip is ready to stream. Only when STREAMON is called
, Vaibhav
Cc: linux-media@vger.kernel.org; Jadav, Brijesh R; Karicheri, Muralidharan
Subject: Re: [PATCH 6/6] TVP514x:Switch to automode for s_input/querystd
On Tuesday 10 November 2009 06:49:55 Hiremath, Vaibhav wrote:
-Original Message-
From: Hans Verkuil [mailto:hverk...@xs4all.nl
Inc.
Germantown, MD 20874
phone: 301-407-9583
email: m-kariche...@ti.com
-Original Message-
From: Hans Verkuil [mailto:hverk...@xs4all.nl]
Sent: Wednesday, November 11, 2009 2:21 AM
To: Karicheri, Muralidharan
Cc: linux-media@vger.kernel.org; davinci-linux-open-
sou...@linux.davincidsp.com
Hans,
[MK] Could you explain this to me? In my prototype, I had tvp5146 that
implements S_STD and tvp7002 that implements S_PRESET. Since bridge
driver
has all the knowledge about the sub devices and their capabilities, it
can
set the flag for each of the input that it supports (currently I
Texas Instruments Inc.
Germantown, MD 20874
phone: 301-407-9583
email: m-kariche...@ti.com
-Original Message-
From: Hans Verkuil [mailto:hverk...@xs4all.nl]
Sent: Wednesday, November 11, 2009 2:21 AM
To: Karicheri, Muralidharan
Cc: linux-media@vger.kernel.org; davinci-linux-open-
sou
Hi Laurent,
I have also copied Vaibhav from TI in this email since this is
of interesting to his area of work as well.
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
email: m-kariche...@ti.com
Who is working on the CCDC driver for OMAP35xx?
Just for
Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
phone: 301-407-9583
email: m-kariche...@ti.com
-Original Message-
From: Guennadi Liakhovetski [mailto:g.liakhovet...@gmx.de]
Sent: Wednesday, November 04, 2009 11:49 AM
To: Karicheri, Muralidharan
Cc: Linux Media
Hi Neil,
Interesting use case. I am thinking of doing the same for
vpfe capture drive and here is what I am thinking of doing.
1) sensor driver MT9P031 configures either full capture(2592x1944)
(No skipping or binning) and video mode (VGA or 480p or any other
resolution through skipping
Guennadi,
Thanks for the reply.
+};
+
+static struct soc_camera_ops mt9t031_ops = {
+ .set_bus_param = mt9t031_set_bus_param,
+ .query_bus_param= mt9t031_query_bus_param,
+ .controls = mt9t031_controls,
+ .num_controls =
: Friday, October 30, 2009 4:32 PM
To: Karicheri, Muralidharan
Cc: Linux Media Mailing List; Hans Verkuil; Laurent Pinchart; Sakari Ailus
Subject: RE: [PATCH 2/9] v4l: add new v4l2-subdev sensor operations, use
g_skip_top_lines in soc-camera
On Fri, 30 Oct 2009, Karicheri, Muralidharan wrote
To: Linux Media Mailing List
Cc: Hans Verkuil; Laurent Pinchart; Sakari Ailus; Karicheri, Muralidharan
Subject: [PATCH/RFC 0/9 v2] Image-bus API and accompanying soc-camera
patches
Hi all
As discussed yesterday, we sant to finalise the conversion of soc-camera
to v4l2-subdev. The presented 9 patches
Guennadi,
mt9m111-rect.left = MT9M111_MIN_DARK_COLS;
mt9m111-rect.top = MT9M111_MIN_DARK_ROWS;
diff --git a/drivers/media/video/mt9t031.c b/drivers/media/video/mt9t031.c
index 6966f64..57e04e9 100644
--- a/drivers/media/video/mt9t031.c
+++ b/drivers/media/video/mt9t031.c
Message-
From: Guennadi Liakhovetski [mailto:g.liakhovet...@gmx.de]
Sent: Friday, October 30, 2009 10:02 AM
To: Linux Media Mailing List
Cc: Hans Verkuil; Laurent Pinchart; Sakari Ailus; Karicheri, Muralidharan
Subject: [PATCH/RFC 9/9] mt9t031: make the use of the soc-camera client API
optional
Acked-by Muralidharan Karicheri m-kariche...@ti.com
Mauro, could you please merge this to your v4l-dvb tree?
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
email: m-kariche...@ti.com
-Original Message-
From: linux-media-ow...@vger.kernel.org
Pawel,
We have been using USERPTR IO in our vpfe capture driver. I also want to
acknowledge the fact that the core layer expects index contrary to API
specs as you have pointed
Even if that was the case though, would an application be supposed to
arbitrarily choose what index to pass? If so,
Kluin [mailto:roel.kl...@gmail.com]
Sent: Monday, October 26, 2009 7:25 AM
To: Mauro Carvalho Chehab; linux-media@vger.kernel.org; Andrew Morton;
Karicheri, Muralidharan
Subject: [PATCH] V4L/DVB: keep index within bound in vpfe_cropcap()
If vpfe_dev-std_index equals ARRAY_SIZE(vpfe_standards
Hans,
following IOCTLS :-
- verify the new v4l2_input capabilities flag added
- Enumerate available presets using VIDIOC_ENUM_DV_PRESETS
- Set one of the supported preset using VIDIOC_S_DV_PRESET
- Get current preset using VIDIOC_G_DV_PRESET
- Detect current preset using
Hans,
#defineV4L2_DV_INVALID0x
#define V4L2_DV_480I59_94 0x0001
#define V4L2_DV_480I60 0x0002
#define V4L2_DV_480P23_976 0x0003
#define V4L2_DV_480P24 0x0004
#define V4L2_DV_480P29_97
Hans,
/* timing data values specified by various standards such as BT.1120,
BT.656 etc. */
/* bt.656/bt.1120 timing data */
struct v4l2_bt_timings {
__u32 interlaced;
__u64 pixelclock;
__u32 width, height;
__u32 polarities;
__u32
, Snehaprabha; Karicheri, Muralidharan; Diego Dompe;
todd.fisc...@ridgerun.com; Grosen, Mark; Linux Media Mailing List
Subject: [PATCH 0/6 v5] Support for TVP7002 in DM365
This series of patches provide support for the TVP7002 decoder in DM365.
Support
includes:
* Inclusion of the chip in v4l2 definitions
Acked-by Muralidharan Karicheri m-kariche...@ti.com
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
email: m-kariche...@ti.com
-Original Message-
From: linux-media-ow...@vger.kernel.org [mailto:linux-media-
ow...@vger.kernel.org] On Behalf Of
Kevin,
I would like to wait on this one and re-submit a revised patch. There is a plan
to use sub device model for ccdc driver. So I will re-submit the ccdc drivers
with this change as well as the corresponding platform code.
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Vaibhav,
Thanks for the patch. See my comment below.
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
phone: 301-407-9583
email: m-kariche...@ti.com
-Original Message-
From: davinci-linux-open-source-boun...@linux.davincidsp.com
Hans,
Well, it is definitely not possible to do it in this manner since changing
the size of struct v4l2_buffer will break the API. Furthermore, something
like
this will only work if the DMA engine can handle strides. Is that the case
for your hardware? I don't think you mentioned what the
...@vger.kernel.org] On Behalf Of Karicheri, Muralidharan
Sent: Thursday, October 15, 2009 10:00 AM
To: Hans Verkuil; Jun Nie
Cc: g.liakhovet...@gmx.de; linux-media
Subject: RE: Support on discontinuous planer buffer and stride
Hans,
Well, it is definitely not possible to do it in this manner since
Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
email: m-kariche...@ti.com
-Original Message-
From: Hans Verkuil [mailto:hverk...@xs4all.nl]
Sent: Saturday, October 10, 2009 2:39 PM
To: Karicheri, Muralidharan
Cc: linux-media@vger.kernel.org
Subject: Re: RFC (v1.1): V4L
Hans,
From: Hans Verkuil [hverk...@xs4all.nl]
Sent: Friday, October 09, 2009 10:43 AM
To: Karicheri, Muralidharan
Cc: linux-media@vger.kernel.org
Subject: Re: RFC (v1.1): V4L - Support for video timings at the input/output
interface
i Murali,
Reading
Hello,
Here is the version 1.1 of the RFC which will be used for implementing
the video timing APIs in the V4L2 core. Please review and let me know
if I have missed something. Following are the changes incorporated in this
version :-
1) Added width and height parameters in the struct
Marek,
As we have seen in the discussion, this is not a streaming device, rather
a transaction/conversion device which operate on a given frame to get a
desired output frame. Each
transaction may have it's own set of configuration context which will be
applied to the hardware
before starting
Marek,
How the hardware is actually designed? I see two possibilities:
1.
[input buffer] --[dma engine] [resizer1] --[dma]- [mem output
buffer1]
\- [resizer2] --[dma]- [mem output
buffer2]
This is the case.
2.
[input buffer] ---[dma engine1]- [resizer1]
1. How to set different color space or size for input and output buffer
each? It could be solved by adding a set of ioctls to get/set source
image format and size, while the existing v4l2 ioctls would only refer
to the output buffer. Frankly speaking, we don't like this idea.
I think that
Ivan,
There is another use case where there are two Resizer hardware working on
the same input frame and give two different output frames of different
resolution. How do we handle this using the one video device approach you
just described here?
what is the difference?
- you can have only
]
Sent: Monday, October 05, 2009 4:14 PM
To: Karicheri, Muralidharan
Cc: Marek Szyprowski; linux-media@vger.kernel.org;
kyungmin.p...@samsung.com; Tomasz Fujak; Pawel Osciak
Subject: RE: Mem2Mem V4L2 devices [RFC]
Hi,
On Mon, 2009-10-05 at 15:02 -0500, Karicheri, Muralidharan wrote:
1. How
Hi Guennadi,
I am currently integrating latest MT9T031 driver to vpfe_capture driver and see
following issues:-
1) Currently MT9T031 Kconfig configuration variable has a dependency on
SOC_CAMERA. We need to remove this dependency since this sensor can be used on
other platforms like
Hi,
In the plumbers conference, a Google group was setup to share ideas/patches
during development of media controller framework. But I have not any email
regarding the same. Could someone tell me what is the current status of this
group and add me to the group based on my below information?
, Muralidharan; linux-media@vger.kernel.org
Cc: Nagendra, Gururaj
Subject: RE: status of google group created for working on Media
controller?
Hi Murali,
-Original Message-
From: linux-media-ow...@vger.kernel.org
[mailto:linux-media-ow...@vger.kernel.org] On Behalf Of
Karicheri
, 2009 12:13 PM
To: Aguirre Rodriguez, Sergio Alberto; Karicheri, Muralidharan; linux-
me...@vger.kernel.org
Subject: RE: status of google group created for working on Media
controller?
Murali,
Please send a subscribe request to linux...@googlegroups.com
Let's make progress from where we left off
: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com]
Sent: Wednesday, September 30, 2009 4:03 AM
To: Peter Huewe
Cc: Jiri Kosina; kernel-janit...@vger.kernel.org; Hans Verkuil; Andy Walls;
Mauro Carvalho Chehab; Steven Toth; Michael Krufky; Karicheri,
Muralidharan; Martin Dauskardt; Beholder
Hi,
First of all, based on Media controller proposal, you would be better
off by developing ISP also as a sub device. This way you will be able
to make connection as below...
sensor - isp - video node
Please check out the bus parameter settings RFC from Hans. Some of these
parameters are set
-ow...@vger.kernel.org [mailto:linux-media-
ow...@vger.kernel.org] On Behalf Of Karicheri, Muralidharan
Sent: Monday, September 28, 2009 11:25 AM
To: Yu, Jinlu; Mauro Carvalho Chehab
Cc: linux-media@vger.kernel.org
Subject: RE: [PATCH 0/5] V4L2 patches for Intel Moorestown Camera Imaging
Hi,
First
Jean-Philippe François,
Component analog input/output interface - ED/HD video
DVI - Digital only, ANALOG only, DVI integrated that support Digital and
Analog; Dual Link - Where second data link is used for higher
bandwidth
SDI - Serial digital interface standardized by SMPTE
HDMI
Laurent,
Thanks for working on this. I might need some more time to review this
as there are many RFCs put for review (including one from myself). From
TI's point of view we need something like a global buffer allocator for video
drivers.
Two ideas that came up while discussing this internally
Hans,
I was busy with some of the merge work and also some other issues.
So this delayed response...
Thanks for your work on this!
You are most welcome !
Where preset is one of the following values:-
#defineV4L2_DV_CUSTOM0x
#define V4L2_DV_480I59_94
Hi,
6. HDMI requires additional investigation. HDMI defines a whole bunch of
infoframe fields. Most of these can probably be exported as
controls?? Is
HDMI audio handled by alsa?
7. how does this interface/co-exist with something like DSS2 on the omap3?
who will own e.g. HDMI setup,
And as I explained above, a v4l2_subdev just implements an interface. It
has
no relation to devices. And yes, I'm beginning to agree with you that
subdevice
was a bad name because it suggested something that it simply isn't.
That said, I also see some advantages in doing this. For statistics
Mauro,
Why have you not included the vpif and vpfe drivers under davinci
in this drop? Or is it being included in another pull request?
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
new phone: 301-407-9583
Old Phone : 301-515-3736 (will be deprecated)
-Original Message-
From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com]
Sent: Tuesday, September 15, 2009 4:17 AM
To: Karicheri, Muralidharan
Cc: Linux Media Mailing List
Subject: Re: Handling second output from vpfe capture - Any suggestion ?
Hi Murali,
sorry for the late
2) Some of the newer SoC devices can connect or disconnect internal
components
dynamically. As an example, the omap3 can either connect a sensor output to
a
CCDC module to a previewer module to a resizer module and finally to a
capture
device node. But it is also possible to capture the sensor
To: Karicheri, Muralidharan
Cc: Linus Torvalds; Andrew Morton; linux-ker...@vger.kernel.org; linux-
me...@vger.kernel.org
Subject: Re: [GIT PATCHES for 2.6.32] V4L/DVB updates
Em Tue, 15 Sep 2009 08:13:20 -0500
Karicheri, Muralidharan m-kariche...@ti.com escreveu:
Mauro,
Why have you not included
Hi,
In our experience, sysfs was useful for simple control mechanism such as
enable/disable or displaying statistics or status. But we had received
customer complaints that with this approach, these functionality will become
unavailable when kernel is built without sysfs as part of size
RFC: V4L - Support for video timings at the input/output interface
Thanks to Hans Verkuil for his initial proposal and feedbacks to help write
this RFC.
Version : 1.0
Background
---
Currently v4l2 specification supports capturing video frames from TV signals
using tuners (input type
Video timings
-
Once the bus is configured and the data format is set it is finally
possible
to determine what resolutions and framerates are supported. Here we run
into
a problem, though. The current V4L2 API is not clear on how that should
be
done.
We have three
Hans,
I haven't gone through the RFC, but thought will respond to the below comment.
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
new phone: 301-407-9583
Old Phone : 301-515-3736 (will be deprecated)
email: m-kariche...@ti.com
I may be mistaken, but I
Hans,
Thanks for your reply..
What you mean by controlling the board?
In general: the media controller can do anything except streaming. However,
that is an extreme position and in practice all the usual ioctls should
remain supported by the video device nodes.
We have currently ported
Hi,
I am working on to add additional capabilities to vpfe capture driver to allow
capture two frames simultaneously for each received frame from the input video
decoder or sensor device. This is done using the IPIPE and Resizer hw available
in DM355. In our internal release this is done by
; Laurent Pinchart; Karicheri, Muralidharan
Subject: Re: [PATCH 0/3] image-bus API
Hi all
Now that we definitely know on the OMAP 3 example, that a parameter like
packing is indeed needed to fully describe video on-the-bus data, I
haven't heard any more objections against my proposed API, so
Hans,
My last proposal merged subdev and bridge parameters into one struct, thus
completely describing the bus setup. I realized that there is a problem
with
that if you have to define the bus for sub-devices that are in the middle
of
a chain: e.g. a sensor sends its video to a image processing
Up to now I usually saw the master-slave relationship defined as per
whether the protocol is master or slave, which always was used from
the PoV of the bridge. I.e., even in a camera datasheet a phrase like
supports master-parallel mode means supports a mode in which the bridge
is a master
Master/Slave is always confusing to me. In VPFE, it can act as master
(when it output sync signal and pixel clock) and slave (when it get sync
signal from sensor/decoder). We use VPFE as slave and sensor/decoder will
provide the pixel clock and sync signal. Please confirm if this is what
Sakari,
The bus type should be definitely included. If a bridge has several
different receivers, say parallel, CSI1 and CSI2, which of them should
be configured to receive data unless that's part of the bus configuration?
I agree and I have responded to have it included in the RFC.
This
Vaibhav,
A minor correction
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
new phone: 301-407-9583
Old Phone : 301-515-3736 (will be deprecated)
email: m-kariche...@ti.com
-Original Message-
From: linux-media-ow...@vger.kernel.org
...@deeprootsystems.com]
Sent: Wednesday, August 26, 2009 5:00 AM
To: Karicheri, Muralidharan; Mauro Carvalho Chehab
Cc: linux-media@vger.kernel.org; Hans Verkuil; DaVinci
Subject: davinci vs. v4l2: lots of conflicts in merge for linux-next
OK, this has gotten a bit out of control, to the point where I cannot
solve
-Original Message-
From: Santiago Nunez-Corrales [mailto:snu...@ridgerun.com]
Sent: Wednesday, August 26, 2009 10:48 AM
To: Linux Media Mailing List; Karicheri, Muralidharan
Subject: Official/Staging git tree for v4l2?
Good morning,
I am currently giving support to the TV7002 driver in dm365
Guennadi,
How is this different from enum_fmt() sub device operation. The pixel format
does specify how bridge device pack the data from sub device into memory
and describe the same to user space applications. Not sure why we need this.
Murali Karicheri
Software Design Engineer
Texas
...@infradead.org]
Sent: Sunday, August 23, 2009 11:10 PM
To: Karicheri, Muralidharan
Cc: Kevin Hilman; Mauro Carvalho Chehab; linux-media@vger.kernel.org; Hans
Verkuil
Subject: Re: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif
capture driver
Em Thu, 20 Aug 2009 16:27:40 -0500
Karicheri
Message-
From: Mauro Carvalho Chehab [mailto:mche...@infradead.org]
Sent: Thursday, August 20, 2009 12:33 AM
To: Karicheri, Muralidharan; Kevin Hilman
Cc: Karicheri, Muralidharan; Mauro Carvalho Chehab; linux-
me...@vger.kernel.org; khil...@deeprootsystems.com; Hans Verkuil
Subject: Re: [PATCH
, August 19, 2009 5:04 PM
To: davinci-linux-open-sou...@linux.davincidsp.com
Cc: Karicheri, Muralidharan; linux-media@vger.kernel.org
Subject: Re: [PATCH 3/5 - v3] DaVinci: platform changes to support vpfe
camera capture
On Monday 17 August 2009, m-kariche...@ti.com wrote:
static struct i2c_board_info
Hans,
You have done a great job in putting up a quick proposal. I was just trying to
understand the intentions/rational behind your proposal to be on the same page.
Thanks for the education. I think this will help others as well.
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Texas Instruments Inc.
Germantown, MD 20874
new phone: 301-407-9583
Old Phone : 301-515-3736 (will be deprecated)
email: m-kariche...@ti.com
-Original Message-
From: Hans Verkuil [mailto:hverk...@xs4all.nl]
Sent: Tuesday, August 18, 2009 2:51 AM
To: Karicheri, Muralidharan
Cc: linux-media
Instruments Inc.
Germantown, MD 20874
new phone: 301-407-9583
Old Phone : 301-515-3736 (will be deprecated)
email: m-kariche...@ti.com
-Original Message-
From: Mauro Carvalho Chehab [mailto:mche...@infradead.org]
Sent: Tuesday, August 18, 2009 1:28 PM
To: Karicheri, Muralidharan
Cc: Mauro
Hans,
Last week, I had sent vpfe capture (v2) and vpif capture(v1) patches for
review. If they look good, please merge them to your tree and send a pull
request to Mauro at your earliest convenience.
Thanks.
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown, MD 20874
[mailto:hverk...@xs4all.nl]
Sent: Saturday, August 15, 2009 8:10 AM
To: Karicheri, Muralidharan
Cc: linux-media@vger.kernel.org; davinci-linux-open-
sou...@linux.davincidsp.com; khil...@deeprootsystems.com
Subject: Re: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif
capture driver
On Friday 14
Vaibhav,
I don't see any serious issues raised here. I can send another patch to fix
this if needed.
Regards,
Murali
+#include linux/spinlock.h
#include linux/kernel.h
+#include linux/io.h
[Hiremath, Vaibhav] You may want to put one line gap here.
Ok. Just editorial.
+#include
, Vaibhav
Sent: Monday, August 17, 2009 12:35 PM
To: Karicheri, Muralidharan; linux-media@vger.kernel.org
Cc: davinci-linux-open-sou...@linux.davincidsp.com; hverk...@xs4all.nl
Subject: RE: [PATCH v1 - 4/5] V4L : vpif updates for DM6467 vpif capture
driver
H Murali,
-Original Message-
From
[mailto:hverk...@xs4all.nl]
Sent: Monday, August 17, 2009 2:47 PM
To: Karicheri, Muralidharan
Cc: linux-media@vger.kernel.org; davinci-linux-open-
sou...@linux.davincidsp.com; khil...@deeprootsystems.com
Subject: Re: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif
capture driver
On Monday 17
: 301-515-3736 (will be deprecated)
email: m-kariche...@ti.com
-Original Message-
From: Hans Verkuil [mailto:hverk...@xs4all.nl]
Sent: Monday, August 17, 2009 2:47 PM
To: Karicheri, Muralidharan
Cc: linux-media@vger.kernel.org; davinci-linux-open-
sou...@linux.davincidsp.com; khil
, Muralidharan
Sent: Monday, August 17, 2009 7:19 PM
To: linux-media@vger.kernel.org
Cc: davinci-linux-open-sou...@linux.davincidsp.com; hverk...@xs4all.nl;
Karicheri, Muralidharan
Subject: [PATCH 1/5 - v3] Adding new fields to add the vpfe capture
enhancements
From: Muralidharan Karicheri m-kariche
: Hans Verkuil [mailto:hverk...@xs4all.nl]
Sent: Monday, August 17, 2009 4:27 PM
To: Karicheri, Muralidharan
Cc: linux-media@vger.kernel.org; davinci-linux-open-
sou...@linux.davincidsp.com; khil...@deeprootsystems.com
Subject: Re: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif
capture
101 - 200 of 290 matches
Mail list logo
