On Mon, Aug 11, 2014 at 2:26 PM, Mark Brown broonie@kernel.org wrote:
On Mon, Aug 11, 2014 at 02:24:31PM -0400, jonsmirl@gmail.com wrote:
On Mon, Aug 11, 2014 at 2:19 PM, Mark Brown broonie@kernel.org wrote:
That really doesn't solve the problem - consider reparenting for example.
Maybe it is time to get rid of setsysclk and use the clk infrastructure? With the clk stuff the order is known by walking the clk dependency chain.
In my case both sgtl5000 and Allwinner I2S are using clk. But there is no mechanism for telling ASOC to use this chain to figure out the ordering.
The clock API is not available on all architectures and it *still* doesn't solve the parenting problems I've repeatedly mentioned.
Ok, I though the reparenting support in the clock system was enough. I was thinking that the clock chain could be run on each call which would dynamically control the ordering. So when you change the parent, the clock chain changes and then the ALSA order would change to follow.