[alsa-devel] Ordering in soc_pcm_hw_params()

[jonsmirl at gmail.com]

On Mon, Aug 11, 2014 at 2:19 PM, Mark Brown <broonie at kernel.org> wrote:
> On Mon, Aug 11, 2014 at 02:00:22PM -0400, jonsmirl at gmail.com wrote:
>> On Mon, Aug 11, 2014 at 1:11 PM, Mark Brown <broonie at kernel.org> wrote:
>
>> > That's absolutely fine, the clocking arrangements and sequencing
>> > requirements for achieving it are in general going to depend on the
>> > machine.  The machine may have requirements which mean that it doesn't
>> > want to use a clock configuration it's physically possible for it to
>> > generate, or it may want to do more extensive reparenting depending on
>> > use case.
>
>> We probably need something like EPROBE_DEFER that is used in the
>> driver subsystem to allow that various pieces to so this out.
>
> 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.



-- 
Jon Smirl
jonsmirl at gmail.com