From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Chris Chiu <chris.chiu@canonical.com>
Cc: pierre-louis.bossart@linux.intel.com,
liam.r.girdwood@linux.intel.com, yang.jie@linux.intel.com,
broonie@kernel.org, Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: No sound cards detected on Kabylake laptops after upgrade to kernel 5.8
Date: Thu, 11 Mar 2021 08:58:57 +0100 [thread overview]
Message-ID: <4ec526eb-cb2e-e0e3-8f23-6f7a25b9919b@intel.com> (raw)
In-Reply-To: <CABTNMG1bO2AJLY0o58TX2=1QZPnPsZXabtYZA01QyqDS40JORg@mail.gmail.com>
On 2021-03-11 6:50 AM, Chris Chiu wrote:
> On Tue, Mar 9, 2021 at 11:29 PM Cezary Rojewski
> <cezary.rojewski@intel.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
next prev parent reply other threads:[~2021-03-11 8:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 12:19 Chris Chiu
2021-03-09 15:29 ` Cezary Rojewski
2021-03-11 5:50 ` Chris Chiu
2021-03-11 7:58 ` Cezary Rojewski [this message]
2021-03-11 10:24 ` Jaroslav Kysela
2021-03-11 10:40 ` Amadeusz Sławiński
2021-03-11 14:10 ` Jaroslav Kysela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ec526eb-cb2e-e0e3-8f23-6f7a25b9919b@intel.com \
--to=cezary.rojewski@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=chris.chiu@canonical.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.com \
--cc=yang.jie@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®