From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Naveen Manohar <naveen.m@intel.com>,
alsa-devel@alsa-project.org, subhransu.s.prusty@intel.com,
pierre-louis.bossart@intel.com
Subject: Re: [PATCH RESEND 1/2] ASoC: Intel: kbl: Remove option of choosing CH count based on pdata
Date: Thu, 30 Nov 2017 09:32:08 +0530 [thread overview]
Message-ID: <20171130040204.GK32417@localhost> (raw)
In-Reply-To: <20171129123314.4x4giq4hk2ew2zol@sirena.org.uk>
On Wed, Nov 29, 2017 at 12:33:14PM +0000, Mark Brown wrote:
> On Wed, Nov 15, 2017 at 03:37:42PM +0530, Naveen Manohar wrote:
> > Remove option of choosing channel count based on pdata for
> > kbl_rt5663_max98927 machine driver.
> > As User-space expects 4ch DMIC data and uses channel-map in ucm to
> > figure-out the desired channel to use, Hence removing driver change
> > to allow choosing channels.
>
> To repeat my previous question which I don't seem to see a response to:
>
> | Which userspace and are you sure there are no boards that only have two
> | of the mics?
I am not sure why Naveen didn't respond, I will ask around.
FWIW the userspace in question is CRAS. CRAS wants to manage MICs and would
*know* how many MICs are on the board and would work with PCM data
accordingly...
--
~Vinod
next prev parent reply other threads:[~2017-11-30 3:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1510740463-21655-1-git-send-email-naveen.m@intel.com>
2017-11-17 3:35 ` [PATCH RESEND 0/2] ASoC: Intel: kbl: update dmic fixup params Vinod Koul
[not found] ` <1510740463-21655-2-git-send-email-naveen.m@intel.com>
2017-11-29 12:33 ` [PATCH RESEND 1/2] ASoC: Intel: kbl: Remove option of choosing CH count based on pdata Mark Brown
2017-11-30 4:02 ` Vinod Koul [this message]
2017-11-30 6:14 ` [alsa-devel] " Naveen M
2017-11-30 11:15 ` Mark Brown
2017-11-30 14:53 ` Pierre-Louis Bossart
2017-12-01 8:53 ` M, Naveen
2017-11-30 6:14 ` Naveen M
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=20171130040204.GK32417@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=naveen.m@intel.com \
--cc=pierre-louis.bossart@intel.com \
--cc=subhransu.s.prusty@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;
as well as URLs for NNTP newsgroup(s).