From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Chris Chiu <chris.chiu@canonical.com>,
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>
Cc: 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: Tue, 9 Mar 2021 16:29:13 +0100 [thread overview]
Message-ID: <dba864a6-1442-1ebc-9de0-8c1511682b70@intel.com> (raw)
In-Reply-To: <CABTNMG31sH99P0F7EKhpFwJf99x4U-VjFWrwXVe1wkra6owFLw@mail.gmail.com>
On 2021-03-09 1:19 PM, Chris Chiu wrote:
> Hi Guys,
> We have received reports that on some Kabylake laptops (Acer Swift
> SF314-54/55 and Lenovo Yoga C930...etc), all sound cards no longer be
> detected after upgrade to kernel later than 5.8. These laptops have
> one thing in common, all of them have Realtek audio codec and connect
> the internal microphone to DMIC of the Intel SST controller either
> [8086:9d71] or [8086:9dc8]. Please refer to
> https://bugzilla.kernel.org/show_bug.cgi?id=201251#c246 and
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117.
>
> From the dmesg from kernel 5.8, the sound related parts only show
> as follows but the expected snd_hda_codec_realtek and the snd_soc_skl
> are not even loaded then.
> [ 13.357495] snd_hda_intel 0000:00:1f.3: DSP detected with PCI
> class/subclass/prog-if info 0x040100
> [ 13.357500] snd_hda_intel 0000:00:1f.3: Digital mics found on
> Skylake+ platform, using SST driver
>
> Building the kernel with the CONFIG_SND_SOC_INTEL_KBL removed can
> load the snd_hda_codec_realtek successfully and the pulseaudio and
> alsa-utils can detect the sound cards again. The result of bisecting
> between kernel 5.4 and 5.8 also get similar result, reverting the
> commit "ALSA: hda: Allow SST driver on SKL and KBL platforms with
> DMIC" can fix the issue. I tried to generate the required firmware for
> snd_soc_skl but it did not help. Please refer to what I did in
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/comments/14
> and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/comments/18.
>
> Since the skl_hda_dsp_generic-tplg.bin and dfw_sst.bin are not in
> the linux-firmware. The Intel SST support for Skylake family is not
> yet complete. Can we simply revert the "ALSA: hda: Allow SST driver on
> SKL and KBL platforms with DMIC" in the current stage and wait for SOF
> support for Skylake family? Or please suggest a better solution for
> this. Thanks
>
> Chris
>
Hello Chris,
Guide: "Linux: HDA+DMIC with skylake driver" [1] should help
understanding history behind the problem as well as fixing it.
Upstream skylake driver - snd_soc_skl - is intended to support HDA DSP +
DMIC configuration via means of snd_soc_skl_hda_dsp machine board
driver. You _may_ switch to legacy HDAudio driver - snd_hda_intel -
losing DMIC support in the process. To remove any confusion - for
Skylake and Kabylake platforms, snd_soc_skl is your option.
Now, due to above, I doubt any skylake-related topology has ever been
upstreamed to linux-firmware as a) most boards are I2S-based, these are
used by our clients which we support via separate channel b) hda
dsp+dmic support on linux for missing until early 2020.
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.
Regards,
Czarek
[1]: https://gist.github.com/crojewsk/4e6382bfb0dbfaaf60513174211f29cb
[2]: https://github.com/alsa-project/alsa-topology-conf/tree/master/topology
next prev parent reply other threads:[~2021-03-09 15:30 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 [this message]
2021-03-11 5:50 ` Chris Chiu
2021-03-11 7:58 ` Cezary Rojewski
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=dba864a6-1442-1ebc-9de0-8c1511682b70@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®