...@ti.com
From: Stijn Devriendt [mailto:high...@gmail.com]
Sent: Saturday, August 15, 2009 2:19 AM
To: Karicheri, Muralidharan; Davinci-linux-open-source@linux.davincidsp.com
Subject: Re: [PATCH v1 - 3/5] V4L : vpif capture driver for DM6467
This code is so EVM specific
, Muralidharan;
Davinci-linux-open-source@linux.davincidsp.com
Subject: RE: [PATCH v1 - 3/5] V4L : vpif capture driver for DM6467
Are we taking care of OMAP L 138 as well, since this chipset has similar VPIF
module, I expect we should be leveraging this code base as is.
Regards,
Khasim
@linux.davincidsp.com
Subject: RE: [PATCH v1 - 3/5] V4L : vpif capture driver for DM6467
Khasim,
I think you are talking about Freon. Yes, the plan is to re-use the driver for
Freon. If there are no register changes, then just adding the vpif
configuration data such as register io address, irq etc
, Muralidharan; Stijn Devriendt;
Davinci-linux-open-source@linux.davincidsp.com
Subject: RE: [PATCH v1 - 3/5] V4L : vpif capture driver for DM6467
Hi Murali,
Thanks for confirming this, I will give a try later this week. Will get in
touch with you.
Regards,
Khasim
From
:40 PM
To: Syed Mohammed, Khasim; Stijn Devriendt;
Davinci-linux-open-source@linux.davincidsp.com
Subject: RE: [PATCH v1 - 3/5] V4L : vpif capture driver for DM6467
Khasim,
Could you let me know what you are trying to do?
Murali Karicheri
Software Design Engineer
Texas Instruments Inc.
Germantown
This code is so EVM specific, instead of SOC-specific.
In order to connect 2 DM646x chips directly via VPIF
this driver requires quite a bit of tweaking.
(I know because I had to do this before ;) )
I'd appreciate a more loosely coupled subdevice layer.
VPIF itself doesn't use I2C so this stuff
...@linux.davincidsp.com] On Behalf Of
Stijn Devriendt
Sent: Saturday, August 15, 2009 11:49 AM
To: Karicheri, Muralidharan; Davinci-linux-open-source@linux.davincidsp.com
Subject: Re: [PATCH v1 - 3/5] V4L : vpif capture driver for DM6467
This code is so EVM specific, instead of SOC-specific.
In order
