[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151106112141.GE18409@sirena.org.uk>
Date: Fri, 6 Nov 2015 11:21:41 +0000
From: Mark Brown <broonie@...nel.org>
To: "Opensource [Adam Thomson]" <Adam.Thomson.Opensource@...semi.com>
Cc: Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Support Opensource <Support.Opensource@...semi.com>
Subject: Re: [PATCH 2/2] ASoC: codecs: Add da7218 codec driver
On Fri, Nov 06, 2015 at 11:11:38AM +0000, Opensource [Adam Thomson] wrote:
> On November 5, 2015 15:28, Mark Brown wrote:
> > > +static int da7218_mic_lvl_det_sw_put(struct snd_kcontrol *kcontrol,
> > > + struct snd_ctl_elem_value *ucontrol)
> > > +{
> > Why is this a user visible control?
> I can envisage in a system you may want to choose which capture channels can
> trigger level detection (if any), and this may change depending on the use-case
> at the time, so having it as a control makes sense to me.
What is a "capture channel" here?
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists