On 06.06.2013 15:56, Mark Brown wrote:
On Thu, Jun 06, 2013 at 03:44:04PM +0200, Daniel Mack wrote:
Would it be an idea to define some commonly used dividers in the core? If they start at 0x80000000, they won't collide with existing ones, and we could simply add them as alternative case statements to existing drivers.
I don't think this is a terribly sensible idea; as soon as you start relying on these dividers in machine code you're going to run into drivers that just don't implement them either due to hardware or due to them being able to figure things out by themselves and...
I do see that we have a way to propagate the sysclk, but how would you determine the bit clock rate from a codec driver?
Also, the same problem with freely definable indices is true for .set_sysclk() as well. Not all drivers expect the actual MCLK rate here.
Daniel