Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Jaroslav Kysela <perex@perex.cz>,
	ALSA development <alsa-devel@alsa-project.org>
Cc: Takashi Iwai <tiwai@suse.de>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: Skylake SST driver - blacklist the PCI device IDs for the auto probe
Date: Fri, 27 Sep 2019 17:31:25 +0200	[thread overview]
Message-ID: <746f82e2-0752-7476-85d7-9cabdd966caa@intel.com> (raw)
In-Reply-To: <20190923165739.3975-1-perex@perex.cz>

On 2019-09-23 18:57, Jaroslav Kysela wrote:
> There are basically three drivers for the PCI devices for
> the recent Intel hardware with the build-in DSPs. The legacy HDA
> driver has dmic_detect module option for the auto detection
> of the platforms with the digital microphone. Because the SOF
> driver is preferred, just skip PCI probe in the Skylake SST
> driver when the PCI device ID clashes by default. The user
> can override the auto behaviour with the pci_binding
> module parameter.
> 

Honestly, the SKL/ SOF/ legacy enumeration is complicated enough and I 
don't think it needs yet enough if or else.

On top of that, some of platforms listed here are shared by both and you 
cannot just enable SOF interface by default there.

> Boot log from Lenovo Carbon X1 (7th gen) with the default settings:
> 
>    snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, aborting probe
>    snd_soc_skl 0000:00:1f.3: SOF driver is preferred on this platform, aborting probe
>    sof-audio-pci 0000:00:1f.3: warning: No matching ASoC machine driver found
>    sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380
>    ....

> 
> Perhaps, it may be more wise to create one shared module and all
> three drivers should call the driver detection routine(s) from one
> place.
> 

This.
It is the only right path to follow.

-

In general there are greater plans ahead as cAVS interface is actually 
the preferred one. That has been already committed by Intel. The details 
of actual merge of both drivers to solve the enumeration-and-other 
issues are still being worked on as that is quite a task : )

Czarek
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      parent reply	other threads:[~2019-09-27 15:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-23 16:57 [alsa-devel] [PATCH] ASoC: Skylake SST driver - blacklist the PCI device IDs for the auto probe Jaroslav Kysela
2019-09-23 18:24 ` Pierre-Louis Bossart
2019-09-23 20:35   ` Jaroslav Kysela
2019-09-23 21:21     ` Takashi Iwai
2019-09-23 23:34       ` Pierre-Louis Bossart
2019-09-24  6:46         ` Jaroslav Kysela
2019-09-24  7:31           ` Takashi Iwai
2019-09-24 13:41           ` Pierre-Louis Bossart
2019-09-24 17:29             ` Jaroslav Kysela
2019-09-24 19:27               ` Pierre-Louis Bossart
2019-09-27 15:31 ` Cezary Rojewski [this message]

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=746f82e2-0752-7476-85d7-9cabdd966caa@intel.com \
    --to=cezary.rojewski@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@perex.cz \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.de \
    /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