>> 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 aggressive clock management, you shouldn't do a >clk_get() every time you do a clk_enable(), same for put. Got you. I am in sync with your thinking. -Murali > >Kevin _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
- RE: [PATCH - v0 2/2] DaVinci - vp... Karicheri, Muralidharan
- RE: [PATCH - v0 2/2] DaVinci - vpfe captu... Karicheri, Muralidharan
- Re: [PATCH - v1 1/2] V4L - vpfe capture - make clo... Kevin Hilman
- RE: [PATCH - v1 1/2] V4L - vpfe capture - mak... Karicheri, Muralidharan
- RE: [PATCH - v1 1/2] V4L - vpfe capture - mak... Karicheri, Muralidharan
- RE: [PATCH - v1 1/2] V4L - vpfe capture -... Karicheri, Muralidharan
- RE: [PATCH - v1 1/2] V4L - vpfe captu... Karicheri, Muralidharan
- Re: [PATCH - v1 1/2] V4L - vpfe c... Kevin Hilman
- RE: [PATCH - v1 1/2] V4L - v... Karicheri, Muralidharan
- Re: [PATCH - v1 1/2] V4L - vpfe capture -... Kevin Hilman
- RE: [PATCH - v1 1/2] V4L - vpfe captu... Karicheri, Muralidharan
