From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.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:21:19 -0600 [thread overview]
Message-ID: <47ec2533-584c-d7f3-4489-e3a043e658e1@linux.intel.com> (raw)
In-Reply-To: <J74DLQ.CON4PD1O51YN@canonical.com>
On 12/14/20 9:54 PM, Kai-Heng Feng wrote:
>
>
> 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.
Re-thinking about this, I actually don't know how this problem occurred:
the tables are conditionally built so you would only select SST if you
had the drivers compiled in.
see sound/hda/intel-dsp-config.c:
/* Kabylake-LP */
#if IS_ENABLED(CONFIG_SND_SOC_INTEL_KBL)
{
.flags = FLAG_SST,
.device = 0x9d71,
.dmi_table = (const struct dmi_system_id []) {
{
.ident = "Google Chromebooks",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "Google"),
}
},
{}
}
},
{
.flags = FLAG_SST | FLAG_SST_ONLY_IF_DMIC,
.device = 0x9d71,
},
#endif
Something's not adding up here.
next prev parent reply other threads:[~2020-12-15 17:22 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
2020-12-15 17:21 ` Pierre-Louis Bossart [this message]
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=47ec2533-584c-d7f3-4489-e3a043e658e1@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;
as well as URLs for NNTP newsgroup(s).