All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
To: "Liao, Bard" <bard.liao@intel.com>,
	Bard Liao <yung-chuan.liao@linux.intel.com>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"tiwai@suse.de" <tiwai@suse.de>
Cc: "linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>
Subject: Re: [PATCH 1/2] ASoC: Intel: sof_sdw: Fix DMI match for Lenovo 83LC
Date: Mon, 6 Jan 2025 10:09:19 -0600	[thread overview]
Message-ID: <834e34eb-b293-49b8-a71f-1ee14f3f9684@linux.dev> (raw)
In-Reply-To: <SJ2PR11MB8424E5B23AF2CFDA5D4D8CDFFF152@SJ2PR11MB8424.namprd11.prod.outlook.com>


>>>> This laptop ships with a different DMI identifier to what was expected,
>>>> and also has the DMICs connected to the host rather than the cs42l43
>>>> codec.
>>>
>>> If the DMICs are connected to the host, isn't there NHLT information
>>> telling the OS how many dmics are connected? If yes, then the
>>> machine-level DMI quirk isn't really needed, all you would need is a
>>> rule that sets it unconditionally when mach->mach_params.dmic_num is
>>> non-zero
>>
>> That is a good idea. However, we also test the case where the PCH DMIC
>> and SoundWire DMIC coexist in the developing stage. Maybe use a quirk
>> for the different DMIC coexist case?
> 
> On second thought, we will eventually create the dai links by reading
> the SDCA functions and remove those DMI quirks. Not sure is it worth
> to change it or even add a new quirk just for temporary used?

If you have any NHLT information, that's a very strong sign that the platform does rely on PCH-connected DMICS.
If you don't then quirks are indeed needed to select PCH or codec-based solutions. I think it's fine to add such quirks for now, it'd be up to Cirrus to remove them later on when all the SDCA parsing is available, which could take a while.

  reply	other threads:[~2025-01-06 16:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02 12:33 [PATCH 0/2] ASoC: Intel: sof_sdw: Fix DMI match entries for a couple of Lenovo laptops Bard Liao
2025-01-02 12:33 ` [PATCH 1/2] ASoC: Intel: sof_sdw: Fix DMI match for Lenovo 83LC Bard Liao
2025-01-02 21:46   ` Pierre-Louis Bossart
2025-01-03  0:16     ` Liao, Bard
2025-01-03  1:39       ` Liao, Bard
2025-01-06 16:09         ` Pierre-Louis Bossart [this message]
2025-01-13 14:09           ` Charles Keepax
2025-01-02 12:33 ` [PATCH 2/2] ASoC: Intel: sof_sdw: Fix DMI match for Lenovo 83JX, 83MC and 83NM Bard Liao
2025-01-15 20:32 ` [PATCH 0/2] ASoC: Intel: sof_sdw: Fix DMI match entries for a couple of Lenovo laptops Mark Brown

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=834e34eb-b293-49b8-a71f-1ee14f3f9684@linux.dev \
    --to=pierre-louis.bossart@linux.dev \
    --cc=bard.liao@intel.com \
    --cc=broonie@kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=tiwai@suse.de \
    --cc=yung-chuan.liao@linux.intel.com \
    /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.