devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Arnaud Pouliquen <arnaud.pouliquen@st.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	huang lin <hl@rock-chips.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Brian Norris <briannorris@chromium.org>,
	Takashi Iwai <tiwai@suse.com>, Rob Herring <robh+dt@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Matthias Kaehlcke <mka@chromium.org>,
	Dylan Reid <dgreid@chromium.org>,
	Bhumika Goyal <bhumirks@gmail.com>
Subject: Re: [PATCH] ASoC: codecs: dmic: Use channel map for configs with a single mic
Date: Fri, 5 Jan 2018 12:04:55 +0000	[thread overview]
Message-ID: <20180105120455.GA9076@sirena.org.uk> (raw)
In-Reply-To: <295ce358-c00e-74ce-50c1-1df32c2c6cf7@st.com>


[-- Attachment #1.1: Type: text/plain, Size: 1162 bytes --]

On Fri, Jan 05, 2018 at 11:45:43AM +0100, Arnaud Pouliquen wrote:

> >> +             num-channels = <1>;

> In your implementation seems not linked to hardware but software...

> DMIC driver description specifies the channels_max to 8 channels.
> I suppose that it is used for DMIC codecs that integrate filters and are
> connected to CPU DAI with I2S/PCM links. But it can be also used for
> DMIC connected to CPU DAI with a SPI link (in this case decimation
> filter in on Soc side).

The intention with the DMIC CODEC is that it's used when the CPU
directly has PDM inputs and the DMICs are just directly wired to it
(stereo is obviously the norm here but some SoCs may bunch things up
further for use with mic arrays).

> If we continue to support both use cases, specify the number of channels
> seems reasonable but this should be use to change the max channel
> constraint, not to declare a control.

Yes, that would seem the most obvious thing - it's how we handle things
like CPU DAIs that support very high channel counts when connected to
stereo CODECs for example.  It's not obvious why we'd use a channel map
here instead.

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

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2018-01-05 12:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04 19:48 [PATCH] ASoC: codecs: dmic: Use channel map for configs with a single mic Matthias Kaehlcke
2018-01-04 19:54 ` Matthias Kaehlcke
2018-01-05 10:45   ` Arnaud Pouliquen
2018-01-05 12:04     ` Mark Brown [this message]
2018-01-05 19:18       ` Matthias Kaehlcke

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=20180105120455.GA9076@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=arnaud.pouliquen@st.com \
    --cc=bhumirks@gmail.com \
    --cc=briannorris@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dgreid@chromium.org \
    --cc=hl@rock-chips.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mka@chromium.org \
    --cc=robh+dt@kernel.org \
    --cc=tiwai@suse.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).