From: Brady Norander <bradynorander@gmail.com>
To: Curtis Malainey <cujomalainey@google.com>
Cc: pierre-louis.bossart@linux.intel.com,
alsa-devel@alsa-project.org, broonie@kernel.org,
cezary.rojewski@intel.com, amadeuszx.slawinski@linux.intel.com,
perex@perex.cz, tiwai@suse.de, cujomalainey@chromium.org
Subject: Re: [PATCH v2] ALSA: hda: intel-dsp-cfg: Add Chromebook quirk to ADL/RPL
Date: Tue, 15 Aug 2023 13:15:37 -0400 [thread overview]
Message-ID: <ZNuyuerb0M6IGRKj@arch> (raw)
In-Reply-To: <CAOReqxjbjkhkqfvTWs9i5NxK6QAsk42Daw1pA_1+b1zG5mbKmQ@mail.gmail.com>
On Tue, Aug 15, 2023 at 09:56:44AM -0700, Curtis Malainey wrote:
> On Tue, Aug 15, 2023 at 8:56 AM Pierre-Louis Bossart <
> pierre-louis.bossart@linux.intel.com> wrote:
> > On 8/15/23 08:52, Brady Norander wrote:
> > > AlderLake and RaptorLake Chromebooks currently use the HDA driver by
> > > default. Add a quirk to use the SOF driver on these platforms, which is
> > > needed for functional internal audio.
> > >
> > > Signed-off-by: Brady Norander <bradynorander@gmail.com>
> >
> > Thanks for the patch
> >
> > Acked-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> >
>
> Now that I am looking closer at the patch, I am very curious why we are not
> hitting the following case and using SOF
The DMIC detection looks for DMIC endpoints in the NHLT, but these
devices don't have NHLT.
next prev parent reply other threads:[~2023-08-16 10:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 13:52 [PATCH v2] ALSA: hda: intel-dsp-cfg: Add Chromebook quirk to ADL/RPL Brady Norander
2023-08-15 15:56 ` Pierre-Louis Bossart
2023-08-15 16:56 ` Curtis Malainey
2023-08-15 17:15 ` Brady Norander [this message]
2023-08-15 18:00 ` Curtis Malainey
2023-08-15 18:28 ` Pierre-Louis Bossart
2023-08-15 19:17 ` Curtis Malainey
2023-08-16 6:38 ` Takashi Iwai
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=ZNuyuerb0M6IGRKj@arch \
--to=bradynorander@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=cujomalainey@chromium.org \
--cc=cujomalainey@google.com \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox