Re: [PATCH - v1 1/2] V4L - vpfe capture - make clocks configurable

2009-12-11 Thread Kevin Hilman
Karicheri, Muralidharan m-kariche...@ti.com writes: Kevin, I think I have figured it out... First issue was that I was adding my entry at the end of dm644x_clks[] array. I need to add it before the CLK(NULL, NULL, NULL) secondly, your suggestion didn't work as is. This is what I had to

RE: [PATCH - v1 1/2] V4L - vpfe capture - make clocks configurable

2009-12-11 Thread Karicheri, Muralidharan
...@deeprootsystems.com] Sent: Friday, December 11, 2009 1:35 PM To: Karicheri, Muralidharan Cc: davinci-linux-open-sou...@linux.davincidsp.com; linux- me...@vger.kernel.org Subject: Re: [PATCH - v1 1/2] V4L - vpfe capture - make clocks configurable Karicheri, Muralidharan m-kariche...@ti.com writes: Kevin, I think

Re: [PATCH - v1 1/2] V4L - vpfe capture - make clocks configurable

2009-12-10 Thread Kevin Hilman
Karicheri, Muralidharan m-kariche...@ti.com writes: Kevin, +/** + * vpfe_disable_clock() - Disable clocks for vpfe capture driver + * @vpfe_dev - ptr to vpfe capture device + * + * Disables clocks defined in vpfe configuration. + */ static void vpfe_disable_clock(struct vpfe_device

Re: [PATCH - v1 1/2] V4L - vpfe capture - make clocks configurable

2009-12-10 Thread Kevin Hilman
Karicheri, Muralidharan m-kariche...@ti.com writes: Kevin, I think I have figured it out... First issue was that I was adding my entry at the end of dm644x_clks[] array. I need to add it before the CLK(NULL, NULL, NULL) secondly, your suggestion didn't work as is. This is what I had to

RE: [PATCH - v1 1/2] V4L - vpfe capture - make clocks configurable

2009-12-10 Thread Karicheri, Muralidharan
I thought following is correct:- Probe() clk_get() followed by clk_enable() Remove() clk_disable() followed by clk_put() Suspend() clk_disable() Resume() clk_enable() Yes, that is correct. I didn't look at the whole driver. My concern was that if the driver was enhanced to more

RE: [PATCH - v1 1/2] V4L - vpfe capture - make clocks configurable

2009-12-10 Thread Karicheri, Muralidharan
Kevin, I think I have figured it out... First issue was that I was adding my entry at the end of dm644x_clks[] array. I need to add it before the CLK(NULL, NULL, NULL) secondly, your suggestion didn't work as is. This is what I had to do to get it working... static struct clk

Re: [PATCH - v1 1/2] V4L - vpfe capture - make clocks configurable

2009-12-09 Thread Kevin Hilman
m-kariche...@ti.com writes: From: Muralidharan Karicheri m-kariche...@ti.com v1 - updated based on comments from Vaibhav Hiremath. On DM365 we use only vpss master clock, where as on DM355 and DM6446, we use vpss master and slave clocks for vpfe capture and AM3517 we use internal clock

RE: [PATCH - v1 1/2] V4L - vpfe capture - make clocks configurable

2009-12-09 Thread Karicheri, Muralidharan
- v1 1/2] V4L - vpfe capture - make clocks configurable m-kariche...@ti.com writes: From: Muralidharan Karicheri m-kariche...@ti.com v1 - updated based on comments from Vaibhav Hiremath. On DM365 we use only vpss master clock, where as on DM355 and DM6446, we use vpss master and slave

RE: [PATCH - v1 1/2] V4L - vpfe capture - make clocks configurable

2009-12-09 Thread Karicheri, Muralidharan
Kevin, +/** + * vpfe_disable_clock() - Disable clocks for vpfe capture driver + * @vpfe_dev - ptr to vpfe capture device + * + * Disables clocks defined in vpfe configuration. + */ static void vpfe_disable_clock(struct vpfe_device *vpfe_dev) { struct vpfe_config *vpfe_cfg =

RE: [PATCH - v1 1/2] V4L - vpfe capture - make clocks configurable

2009-12-09 Thread Karicheri, Muralidharan
...@vger.kernel.org Subject: RE: [PATCH - v1 1/2] V4L - vpfe capture - make clocks configurable Kevin, +/** + * vpfe_disable_clock() - Disable clocks for vpfe capture driver + * @vpfe_dev - ptr to vpfe capture device + * + * Disables clocks defined in vpfe configuration. + */ static void

RE: [PATCH - v1 1/2] V4L - vpfe capture - make clocks configurable

2009-12-09 Thread Karicheri, Muralidharan
Sent: Wednesday, December 09, 2009 1:22 PM To: Karicheri, Muralidharan; Kevin Hilman Cc: davinci-linux-open-sou...@linux.davincidsp.com; linux- me...@vger.kernel.org Subject: RE: [PATCH - v1 1/2] V4L - vpfe capture - make clocks configurable Kevin, I tried the following and I get error

RE: [PATCH - v1 1/2] V4L - vpfe capture - make clocks configurable

2009-12-03 Thread Karicheri, Muralidharan
To: 'Hans Verkuil' Cc: Hiremath, Vaibhav; linux-media@vger.kernel.org Subject: FW: [PATCH - v1 1/2] V4L - vpfe capture - make clocks configurable Hans, Could you please add this to your hg tree and send a pull request to Mauro? This was reviewed by Vaibhav and tested on DM355, DM6446, AM3517

[PATCH - v1 1/2] V4L - vpfe capture - make clocks configurable

2009-12-01 Thread m-karicheri2
From: Muralidharan Karicheri m-kariche...@ti.com v1 - updated based on comments from Vaibhav Hiremath. On DM365 we use only vpss master clock, where as on DM355 and DM6446, we use vpss master and slave clocks for vpfe capture and AM3517 we use internal clock and pixel clock. So this patch makes