All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Jaroslav Kysela <perex@perex.cz>,
	ALSA development <alsa-devel@alsa-project.org>
Cc: Takashi Iwai <tiwai@suse.de>
Subject: Re: [alsa-devel] [PATCH v5 1/2] ALSA: hda: add Intel DSP configuration / probe code
Date: Fri, 25 Oct 2019 09:10:32 -0500	[thread overview]
Message-ID: <69a9c838-24dc-f101-359f-4778dc102f9e@linux.intel.com> (raw)
In-Reply-To: <0036ad81-c383-ec91-5acb-fccf681b538c@perex.cz>


>> Jaroslav, I found a case where the logic doesn't seem to work as 
>> intended.
>>
>> the code currently scans through the table looking for a PCI ID match,
>> and a DMI match for quirks.
>>
>> On a KBL NUC device with the DSP enabled, we go through the entire list
>> without finding a match, which means we return the _ANY flag. so if we
>> try to probe the snd-soc-skl driver, the checks will allow the driver to
>> continue, despite this configuration not being supported.
>>
>> It was my understanding that we would always load the legacy driver
>> *unless* there is a match in the table? If yes, there we can change the
>> default this way:
>>
>> @@ -333,7 +355,7 @@ int snd_intel_dsp_driver_probe(struct pci_dev *pci)
>>           /* find the configuration for the specific device */
>>           cfg = snd_intel_dsp_find_config(pci, config_table,
>> ARRAY_SIZE(config_table));
>>           if (!cfg)
>> -               return SND_INTEL_DSP_DRIVER_ANY;
>> +               return SND_INTEL_DSP_DRIVER_LEGACY;
>>
>> Or we need to add a case where we force the legacy in the table for each
>> platform.
> 
> I would prefer to add another entry to the configuration table without 
> .flags (or .flags = 0) with a comment, why the legacy driver is selected 
> by default even if the DSP is present.

Ah yes, flags == 0 would mean legacy indeed. Will send a patch, thanks 
for the idea.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      reply	other threads:[~2019-10-25 14:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22 17:43 [alsa-devel] [PATCH v5 1/2] ALSA: hda: add Intel DSP configuration / probe code Jaroslav Kysela
2019-10-22 17:43 ` [alsa-devel] [PATCH v5 2/2] ALSA: hda: fix intel DSP config Jaroslav Kysela
2019-10-23  4:34   ` Takashi Iwai
2019-10-23  4:34 ` [alsa-devel] [PATCH v5 1/2] ALSA: hda: add Intel DSP configuration / probe code Takashi Iwai
2019-10-24 20:33 ` Pierre-Louis Bossart
2019-10-25  9:49   ` Jaroslav Kysela
2019-10-25 14:10     ` Pierre-Louis Bossart [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=69a9c838-24dc-f101-359f-4778dc102f9e@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@perex.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.