On Wed, Aug 10, 2016 at 08:57:28AM -0500, Pierre-Louis Bossart wrote: > Without going into a debate on x86 v. the clock API or the merits of a patch > that has already been applied, I am pretty confused on who's supposed to > manage the mclk between the machine and codec driver. > So on a DAPM transition the clock is enabled. Fine. > What's not clear here is that the codec driver doesn't know what rates are > supported by the SOC/chipset. The machine driver is typically the one doing > calls such as This should really be being propagated through the clock tree by the clock API rather than open coded - for a lot of things it'll just boil down to a clk_set_rate() at the edge of the clock tree. Any constraints should also be applied through the clock API, though in a lot of cases the devices are simple enough that it should be a fairly mechanical process. > so the summary is that we have two ways of doing the same thing - turning > the mclk on when it's needed - and I wonder if doing this in the codec is > really the right solution? Again this is not a question on the merits of the > clk API/framework but whether we can have a single point of control instead > of two pieces of code doing the same thing in two drivers. > If I am missing something I am all ears. We've got two ways of doing this at the minute partly because historically things have been open coded in the machine drivers due to the lack of a clock API, now we have one we can use we should be using it consistently to set rates. Where the machine driver needs to do things dynamically it really ought to be able to express the constraints it's trying to set through the clock API, if we can't do things we need we should improve the clock API. This will mean that we don't have to reinvent the wheel when we're doing things with clocks, we have consistent interfaces to all parts of the clock tree and other bits of the system will get reuse from anything we've learned about implementation. The CODEC clearly has *some* idea of what's going on here, and especially for simpler CODECs the code to drive the clocking should be fairly easy to generalize as there's few options. From a clock API point of view the CODEC really ought to be the one requesting the clocks that go into it, though there's nothing that says it has to only use its own information to do that.
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
