[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190117130549.GA16759@sig21.net>
Date: Thu, 17 Jan 2019 14:05:49 +0100
From: Johannes Stezenbach <js@...21.net>
To: Hans de Goede <hdegoede@...hat.com>
Cc: Dean Wallace <duffydack73@...il.com>,
Mogens Jensen <mogens-jensen@...tonmail.com>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Stephen Boyd <sboyd@...nel.org>,
Michael Turquette <mturquette@...libre.com>,
linux-clk <linux-clk@...r.kernel.org>,
Stable <stable@...r.kernel.org>,
Carlo Caione <carlo@...lessm.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Regression found (Stop-marking-clocks-as-CLK_IS_CRITICAL)
On Thu, Jan 17, 2019 at 01:05:35PM +0100, Hans de Goede wrote:
> On 17-01-19 10:12, Dean Wallace wrote:
> > On 17-01-19, Mogens Jensen wrote:
> > > Kernel is compiled with SND_SOC_INTEL_CHT_BSW_MAX98090_TI_MACH and the quirk seems to have fixed the problem caused by commit 648e921888ad ("clk: x86: Stop marking clocks as CLK_IS_CRITICAL"), as sound is now working if running "speaker-test" on my system which is clean ALSA.
>
> Note being "clean ALSA" is really not a good thing now a days,
> for lots of things we depend on pulseaudio (like setting
> up UCM mixer profiles).
FWIW I disagree because PA never worked for me. I simply used
"alsaucm -c chtcx2072x set _verb HiFi". But I was surprised
that PA does the ALSA UCM setup but it's not documented well that
you need to do it by other means if you don't use PA.
https://bugzilla.kernel.org/show_bug.cgi?id=115531#c72
Regards,
Johannes
Powered by blists - more mailing lists