From: Takashi Iwai <tiwai@suse.de>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>
Subject: Re: [PATCH] ASoC: snd-sof-intel-hda-common - add hda_model parameter and pass it to HDA codec driver
Date: Fri, 24 Apr 2020 18:06:38 +0200 [thread overview]
Message-ID: <s5h368sswa9.wl-tiwai@suse.de> (raw)
In-Reply-To: <28900433-f2a7-bf4e-7861-5522f0aedee1@linux.intel.com>
On Fri, 24 Apr 2020 17:44:27 +0200,
Pierre-Louis Bossart wrote:
>
>
>
> >> Hmm, I wonder is this now doing more harm than good. Based on browsing
> >> through the related code in hda-codec.c and friends, it would seem
> >> "sofbus" as the default is mostly harmless, but I could have missed
> >> something.
> >
> > That's currently harmless since no codec driver defines "sofbus"
> > model, hence the HDA parser continues to match with the default
> > quirks. OTOH, the fixed "sofbus" model is fairly useless. So, feel
> > free to take my ack, too:
>
> For my education, are you saying that the default should be that the
> modelname is NULL, and the hda auto parser will use known quirks based
> on PCI/SSID information, and when the user sets the model name to a
> non-NULL string it will force a specific quirk to be used?
Yes. If the given string matches with the pre-defined table, the
quirk entry is used and applied. If no string is given or it doesn't
match, it continues to the fallback quirk, that is, matching with PCI
SSID, then codec SSID.
Takashi
next prev parent reply other threads:[~2020-04-24 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 9:25 [PATCH] ASoC: snd-sof-intel-hda-common - add hda_model parameter and pass it to HDA codec driver Jaroslav Kysela
2020-04-24 12:24 ` Kai Vehmanen
2020-04-24 12:41 ` Takashi Iwai
2020-04-24 15:44 ` Pierre-Louis Bossart
2020-04-24 16:06 ` Takashi Iwai [this message]
2020-04-24 17:01 ` Pierre-Louis Bossart
2020-04-24 17:00 ` 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=s5h368sswa9.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=pierre-louis.bossart@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox