From: Takashi Iwai <tiwai@suse.de>
To: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@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 14:41:17 +0200 [thread overview]
Message-ID: <s5hk125rr82.wl-tiwai@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2004241517530.2957@eliteleevi.tm.intel.com>
On Fri, 24 Apr 2020 14:24:30 +0200,
Kai Vehmanen wrote:
>
> Hey,
>
> On Fri, 24 Apr 2020, Jaroslav Kysela wrote:
>
> > It may be useful to pass the specific model to the generic HDA codec
> > routines like the legacy HDA driver (snd-hda-intel) allows.
> [...]
> > Original proposal: https://lore.kernel.org/alsa-devel/20191203161908.7496-1-perex@perex.cz/
>
> not sure why this got stuck last year, but seems like a welcome
> addition:
>
> Reviewed-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
>
> > The model name "sofbus" is tricky anyway.
>
> 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:
Reviewed-by: Takashi Iwai <tiwai@suse.de>
thanks,
Takashi
next prev parent reply other threads:[~2020-04-24 12:42 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 [this message]
2020-04-24 15:44 ` Pierre-Louis Bossart
2020-04-24 16:06 ` Takashi Iwai
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=s5hk125rr82.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