public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Sasha Levin <sashal@kernel.org>, Takashi Iwai <tiwai@suse.de>,
	ALSA development <alsa-devel@alsa-project.org>,
	stable@vger.kernel.org
Subject: Re: 5.5.y - apply "ASoC: intel/skl/hda - export number of digital microphones via control components"
Date: Wed, 4 Mar 2020 19:38:35 +0000	[thread overview]
Message-ID: <20200304193835.GH5646@sirena.org.uk> (raw)
In-Reply-To: <3b00df9a-6b53-def7-4304-d9829de749c6@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 550 bytes --]

On Wed, Mar 04, 2020 at 01:30:59PM -0600, Pierre-Louis Bossart wrote:
> On 3/4/20 1:06 PM, Mark Brown wrote:

> > Anyway, is my understanding correct that this is fixing a regression
> > caused by switching the default to SOF?

> This is fixing a regression on platforms that have digital microphones,
> where SOF is automatically selected by default. For platforms without DMICs,
> the legacy driver is still used and this patch has no effect.

OK, in that case this should go in then - it's certainly a lot better
than reverting the switch to SOF.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-03-04 19:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04 15:25 5.5.y - apply "ASoC: intel/skl/hda - export number of digital microphones via control components" Jaroslav Kysela
2020-03-04 15:44 ` Mark Brown
2020-03-04 15:53   ` Jaroslav Kysela
2020-03-04 16:09     ` Mark Brown
2020-03-04 17:17       ` Pierre-Louis Bossart
2020-03-04 18:11         ` Mark Brown
2020-03-04 18:50           ` Pierre-Louis Bossart
2020-03-04 19:06             ` Mark Brown
2020-03-04 19:30               ` Pierre-Louis Bossart
2020-03-04 19:38                 ` Mark Brown [this message]
2020-03-06 13:15 ` Sasha Levin

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=20200304193835.GH5646@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --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