From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Hui Wang <hui.wang@canonical.com>,
Curtis Malainey <cujomalainey@google.com>,
alsa-devel@alsa-project.org, broonie@kernel.org,
Daniel Drake <drake@endlessm.com>
Subject: Re: [PATCH 6/6] ALSA: hda/intel: stop probe if DMICS are detected on Skylake+ platforms
Date: Fri, 19 Jul 2019 13:29:10 -0500 [thread overview]
Message-ID: <6bc24e2a-596b-83f4-d022-5f630657c3a1@linux.intel.com> (raw)
In-Reply-To: <s5hlfwtzyca.wl-tiwai@suse.de>
On 7/19/19 1:13 PM, Takashi Iwai wrote:
> On Fri, 19 Jul 2019 19:06:10 +0200,
> Pierre-Louis Bossart wrote:
>>
>> +static int azx_check_dmic(struct pci_dev *pci, struct azx *chip)
>> +{
>> + struct nhlt_acpi_table *nhlt;
>> + int ret = 0;
>> +
>> + if (chip->driver_type == AZX_DRIVER_SKL &&
>> + pci->class != 0x040300) {
>> + nhlt = intel_nhlt_init(&pci->dev);
>> + if (nhlt) {
>> + if (intel_nhlt_get_dmic_geo(&pci->dev, nhlt)) {
>> + ret = -ENODEV;
>> + dev_dbg(&pci->dev, "Digital mics found on Skylake+ platform, aborting probe\n");
>
> IMO, this can be verbose, dev_info() would be suitable.
> Otherwise user has no idea why the module load is skipped.
sure, will do.
>
>
>> @@ -2055,6 +2078,17 @@ static int azx_probe(struct pci_dev *pci,
>> card->private_data = chip;
>> hda = container_of(chip, struct hda_intel, chip);
>>
>> + /*
>> + * stop probe if digital microphones detected on Skylake+ platform
>> + * with the DSP enabled. This is an opt-in behavior defined at build
>> + * time or at run-time with a module parameter
>> + */
>> + if (IS_ENABLED(CONFIG_SND_HDA_INTEL_DETECT_DMIC) || dmic_detect >= 0) {
>
> Isn't it "dmic_detect != 0" ? Otherwise passing dmic_detect=0 would
> be treated as positive here.
Ah, good catch. I literally copied the enable_msi example here, which
relies on >= 0.
if (enable_msi >= 0) {
chip->msi = !!enable_msi;
return;
}
Not sure what the intention was here.
Using dmic_detect != 0 wouldn't work for the default -1 value,
maybe dmic_detect > 0 is probably a better solution?
next prev parent reply other threads:[~2019-07-19 18:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 17:06 [PATCH 0/6] ALSA/HDA: abort probe when DMICs are detected Pierre-Louis Bossart
2019-07-19 17:06 ` [PATCH 1/6] ASoC: Intel: Skylake: move NHLT header to common directory Pierre-Louis Bossart
2019-07-19 17:06 ` [PATCH 2/6] ALSA: hda: move parts of NHLT code to new module Pierre-Louis Bossart
2019-07-19 17:06 ` [PATCH 3/6] ALSA: hda: intel-nhlt: remove useless OR operation Pierre-Louis Bossart
2019-07-19 18:09 ` Takashi Iwai
2019-07-19 18:20 ` Pierre-Louis Bossart
2019-07-19 18:30 ` Takashi Iwai
2019-07-19 17:06 ` [PATCH 4/6] ALSA: hda: intel-nhlt: handle NHLT VENDOR_DEFINED DMIC geometry Pierre-Louis Bossart
2019-07-19 17:06 ` [PATCH 5/6] ASoC: Intel: Skylake: use common NHLT module Pierre-Louis Bossart
2019-07-19 17:06 ` [PATCH 6/6] ALSA: hda/intel: stop probe if DMICS are detected on Skylake+ platforms Pierre-Louis Bossart
2019-07-19 18:13 ` Takashi Iwai
2019-07-19 18:29 ` Pierre-Louis Bossart [this message]
2019-07-19 18:55 ` Takashi Iwai
2019-07-19 20:21 ` Pierre-Louis Bossart
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=6bc24e2a-596b-83f4-d022-5f630657c3a1@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cujomalainey@google.com \
--cc=drake@endlessm.com \
--cc=hui.wang@canonical.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 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.