From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>,
sound-open-firmware@alsa-project.org
Cc: SOUND <alsa-devel@alsa-project.org>
Subject: Re: [Sound-open-firmware] SoF support for 8086:9d71?
Date: Mon, 14 Dec 2020 13:33:16 -0600 [thread overview]
Message-ID: <f05cb5ff-b5b1-2882-ba4a-380e696b2569@linux.intel.com> (raw)
In-Reply-To: <9I9CLQ.GP190FSJBRXK3@canonical.com>
> On more recent kernels legacy HDA stops working for device 8086:9d71:
> [ 47.211381] snd_hda_intel 0000:00:1f.3: DSP detected with PCI
> class/subclass/prog-if info 0x040100
> [ 47.211383] snd_hda_intel 0000:00:1f.3: Digital mics found on
> Skylake+ platform, using SST driver
>
> However, only legacy HDA supports it:
> 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Sunrise
> Point-LP HD Audio [8086:9d71] (rev 21)
> ..
> Kernel modules: snd_hda_intel
>
> Ubuntu kernel doesn't select SND_SOC_INTEL_SKYLAKE, which builds
> snd-soc-skl, because based on the Kconfig description SOF should support
> it.
>
> I wonder if SND_SOC_INTEL_SKYLAKE should be select again?
SOF does not support Skylake and Kabylake, and only the Up2 board for
APL. I am not sure what you mean by 'recent' kernels since this dynamic
selection has been in place for a year now?
At any rate, to make this work again:
1. You can select SND_SOC_INTEL_SKYLAKE or alternatively to be more
accurate:
SND_SOC_INTEL_SKL
SND_SOC_INTEL_APL
SND_SOC_INTEL_KBL
There are known issues with Conexant codecs, typically on HP devices,
only Realtek codecs are supported.
2. In addition you will need to have the topology for SKL/KBL w/ HDaudio
codecs. It's in alsa-topology-conf but would need to be compiled and
installed.
3. UCM files should be already handled in alsa-ucm-conf
Hope this helps
-Pierre
next prev parent reply other threads:[~2020-12-14 19:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 16:51 SoF support for 8086:9d71? Kai-Heng Feng
2020-12-14 19:33 ` Pierre-Louis Bossart [this message]
2020-12-15 3:54 ` [Sound-open-firmware] " Kai-Heng Feng
2020-12-15 17:21 ` Pierre-Louis Bossart
2020-12-15 17:48 ` Amadeusz Sławiński
2020-12-15 17:53 ` Kai-Heng Feng
2020-12-15 17:59 ` Pierre-Louis Bossart
2020-12-16 3:55 ` Kai-Heng Feng
2020-12-17 8:25 ` Kai-Heng Feng
2021-01-12 13:25 ` Amadeusz Sławiński
[not found] ` <CAAd53p7OHhqXDJDuEamXwfseXiUdGfDsJhNJbdUYo_4uoBdzdQ@mail.gmail.com>
2021-01-13 13:44 ` Amadeusz Sławiński
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=f05cb5ff-b5b1-2882-ba4a-380e696b2569@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=kai.heng.feng@canonical.com \
--cc=sound-open-firmware@alsa-project.org \
/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