From: Kai-Heng Feng <kai.heng.feng@canonical.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: SOUND <alsa-devel@alsa-project.org>,
sound-open-firmware@alsa-project.org
Subject: Re: [Sound-open-firmware] SoF support for 8086:9d71?
Date: Tue, 15 Dec 2020 11:54:55 +0800 [thread overview]
Message-ID: <J74DLQ.CON4PD1O51YN@canonical.com> (raw)
In-Reply-To: <f05cb5ff-b5b1-2882-ba4a-380e696b2569@linux.intel.com>
On Mon, Dec 14, 2020 at 13:33, Pierre-Louis Bossart
<pierre-louis.bossart@linux.intel.com> wrote:
>
>> 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
>> \x7fclass/subclass/prog-if info 0x040100
>> [ 47.211383] snd_hda_intel 0000:00:1f.3: Digital mics found on
>> \x7fSkylake+ platform, using SST driver
>>
>> However, only legacy HDA supports it:
>> 00:1f.3 Multimedia audio controller [0401]: Intel Corporation
>> Sunrise \x7fPoint-LP HD Audio [8086:9d71] (rev 21)
>> ..
>> Kernel modules: snd_hda_intel
>>
>> Ubuntu kernel doesn't select SND_SOC_INTEL_SKYLAKE, which builds
>> \x7fsnd-soc-skl, because based on the Kconfig description SOF should
>> support \x7fit.
>>
>> 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?
Ubuntu kernel only changed this in 20.10 release.
>
> 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.
Right, so we can't really enable this for generic distros like Ubuntu.
Let me think of a more generic solution.
Kai-Heng
>
> 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-15 3:56 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 ` [Sound-open-firmware] " Pierre-Louis Bossart
2020-12-15 3:54 ` Kai-Heng Feng [this message]
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=J74DLQ.CON4PD1O51YN@canonical.com \
--to=kai.heng.feng@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=pierre-louis.bossart@linux.intel.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