On Tue, Feb 11, 2020 at 1:18 AM Curtis Malainey <cujomalainey@xxxxxxxxxx> wrote: > > +Fletcher Woodruff > See comment #3 in the bug. This is not a GLK specific issue. If I remember correctly Fletcher found that this was occurring on 2-3 platforms. Yes, I tested this and saw the same bug on a Pixelbook Go which I believe is Comet Lake. >SST has the ability to turn on clocks on demand which is why this has not been an issue previously from what I understand on the bug. > > And that is a fair point, we do need to consider other users of the codec. > > > On Mon, Feb 10, 2020 at 8:07 AM Pierre-Louis Bossart <pierre-louis.bossart@xxxxxxxxxxxxxxx> wrote: >> >> >> >> On 2/10/20 9:44 AM, Curtis Malainey wrote: >> > +Jimmy Cheng-Yi Chiang <cychiang@xxxxxxxxxx> >> > >> > This error is causing pcm_open commands to fail timing requirements, >> > sometimes taking +500ms to open the PCM as a result. This work around is >> > required so we can meet the timing requirements. The bug is explained in >> > detail here https://github.com/thesofproject/sof/issues/2124 >> >> Ah, thanks for the pointer, but this still does not tell me if it's a >> GLK-only issue or not. And if yes, there are alternate proposals >> discussed in that issue #2124, which has been idle since November 25. >> >> What I am really worried is side effects on unrelated platforms. _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
