RE: [PATCH - v0 2/2] DaVinci - vpfe capture - Make clocks configurable

2009-12-08 Thread Karicheri, Muralidharan
Vaibhav, I have posted a re-worked patch with clocks configuration moved to ccdc. From your response below, I understand the clocks are being called differently on different SoCs even though they use the same IP. So IMO, it is better to customize it on a SoC by defining the clock names in the res

RE: [PATCH - v0 2/2] DaVinci - vpfe capture - Make clocks configurable

2009-12-08 Thread Hiremath, Vaibhav
..@xs4all.nl; khil...@deeprootsystems.com > Cc: davinci-linux-open-sou...@linux.davincidsp.com > Subject: RE: [PATCH - v0 2/2] DaVinci - vpfe capture - Make clocks > configurable > > >I was talking to Sekhar about this and actually he made some good > points > >about this implementation

RE: [PATCH - v0 2/2] DaVinci - vpfe capture - Make clocks configurable

2009-12-04 Thread Karicheri, Muralidharan
Vaibhav, Could you confirm my question below? I need to submit a patch on Monday. >>Currently we have vpfe_capture.c file (master/bridge driver) which is >>handling clk_get/put, and platform data is providing the details about it. >>Ideally we should handle it in respective ccdc driver file, sinc

RE: [PATCH - v0 2/2] DaVinci - vpfe capture - Make clocks configurable

2009-12-03 Thread Karicheri, Muralidharan
>I was talking to Sekhar about this and actually he made some good points >about this implementation. > >If we consider specific IP, then the required clocks would remain always be >the same. There might be some devices which may not be using some clocks >(so as that specific feature). > >Actually

RE: [PATCH - v0 2/2] DaVinci - vpfe capture - Make clocks configurable

2009-12-02 Thread Hiremath, Vaibhav
> -Original Message- > From: Karicheri, Muralidharan > Sent: Tuesday, December 01, 2009 10:49 PM > To: linux-media@vger.kernel.org; hverk...@xs4all.nl; > khil...@deeprootsystems.com > Cc: davinci-linux-open-sou...@linux.davincidsp.com; Hiremath, > Vaibhav; Karicheri, Muralidharan > Subject