[alsa-devel] [PATCH] ASoC drivers for the Freescale MPC8610 SoC
timur at freescale.com
Sat Jan 5 13:43:17 EST 2008
Mark Brown wrote:
> Each individual call to set_sysclk() only takes three parameters but it
> can be called repeatedly and some configurations are going to require
In other words, ...
clock1 = <0, bb8000>
clock2 = <1, 653230>
clock23 = <0, ab2372>
> and of course the ordering matters.
Ok, you got me there. But then, isn't this just another example where the
device tree is incapable of describing a complex configuration, and so we need
a platform driver?
> Indeed. Providing the device tree stuff doesn't get set in stone I'm
> not sure we need to nail this down perfectly for ASoC v1 when we're
> running into trouble working around it.
I definitely agree with that. I'll be the first to admit that this driver,
much like ASoC V1, is a prototype.
Linux Kernel Developer @ Freescale
More information about the Linuxppc-dev