Re: [PATCH v1 - 3/5] V4L : vpif capture driver for DM6467

2009-08-15 Thread Stijn Devriendt
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

RE: [PATCH v1 - 3/5] V4L : vpif capture driver for DM6467

2009-08-15 Thread Syed Mohammed, Khasim
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 From: davinci-linux-open-source-boun...@linux.davincidsp.com

Re: [PATCH v1 - 1/5] DaVinci - restructuring code to support vpif capture driver

2009-08-15 Thread Hans Verkuil
On Friday 14 August 2009 23:01:41 m-kariche...@ti.com wrote: From: Muralidharan Karicheri m-kariche...@ti.com This patch makes the following changes:- 1) Modify vpif_subdev_info to add board_info, routing information and vpif interface configuration. Remove addr since it is

da830/omapl137 boot problem caused by clocks

2009-08-15 Thread Koen Kooi
Hi, 2kernel BUG at arch/arm/mach-davinci/time.c:375! 1Unable to handle kernel NULL pointer dereference at virtual address 1pgd = c0004000 it's this bit: timer_clk = clk_get(NULL, timer0); I've seen some talk about not using clocknames and all, but I haven't wrapped my head