On Wed, May 02, 2012 at 08:12:24PM +0800, Shawn Guo wrote:
On Wed, May 02, 2012 at 12:41:22PM +0100, Mark Brown wrote:
The major problem here is that we can't rely on having the clock API present at all on most platforms so as soon as we start adding clock support into things we have to do a performance with HAVE_CLK which is at best annoying.
Is this something that the series below tries to solve?
Well, it helps building but that's only part of the issue - we've still got registration problems and if we were using the API in anger we would need things like clk_set_rate() to actually work. It's not just a case of simply enabling and disabling clocks (which can be stubbed out pretty effectively), audio generally needs to manage the clock rates too.