linux-kernel - Re: No sound cards detected on Kabylake laptops after upgrade to kernel 5.8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 11 Mar 2021 08:58:57 +0100
From:   Cezary Rojewski <cezary.rojewski@...el.com>
To:     Chris Chiu <chris.chiu@...onical.com>
Cc:     pierre-louis.bossart@...ux.intel.com,
        liam.r.girdwood@...ux.intel.com, yang.jie@...ux.intel.com,
        broonie@...nel.org, Takashi Iwai <tiwai@...e.com>,
        alsa-devel@...a-project.org,
        Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: No sound cards detected on Kabylake laptops after upgrade to
 kernel 5.8

On 2021-03-11 6:50 AM, Chris Chiu wrote:
> On Tue, Mar 9, 2021 at 11:29 PM Cezary Rojewski
> <cezary.rojewski@...el.com> wrote:
>>

...

>> Topologies for most common skylake driver configurations:
>> - skl/kbl with i2s rt286
>> - apl/glk with i2s rt298
>> - <any> with hda dsp
>> can be found in alsa-topology-conf [2].
>>
>> Standard, official tool called 'alsatplg' is capable of compiling these
>> into binary form which, after being transferred to /lib/firmware/ may be
>> consumed by the driver during runtime.
>> I have no problem with providing precompiled binaries to linux-firmware,
>> if that's what community wants.

...

> 
> I think the guild [1] is too complicated for normal users to fix the problem.
> Given it's not only the internal microphone being affected, it's no sound
> devices being created at all so no audio functions can work after kernel 5.8.
> 
> Is there any potential problem to built-in the "<any> with hda dsp" precompiled
> binary in linux-firmware?

In general, linux-firmware is not the place to put driver-specific 
configuration files. It'd best to have standard UCM/topology files being 
build and honored during disto image creation.

In regard to the guide, thanks for checking it out. What do you think 
could be improved so that normal user has easier time with it? Feedback 
is much appreciated.

Regards,
Czarek