[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2E89032DDAA8B9408CB92943514A0337D460CC6C@SW-EX-MBX01.diasemi.com>
Date: Mon, 9 Nov 2015 12:28:39 +0000
From: "Opensource [Adam Thomson]" <Adam.Thomson.Opensource@...semi.com>
To: Mark Brown <broonie@...nel.org>,
"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 November 8, 2015 10:34, Mark Brown wrote:
> > > Hang on, is this just recording a DC value with the ADC and then looking
> > > at that?
>
> > The RMS of the Mic signal is taken and compared to the trigger level set. If
> > it's above that level then an IRQ is raised.
>
> What I'm trying to figure out here is if this depends on the audio
> routing at runtime or if it's got dedicated configuration?
This feature is available for any/all mics connected. Which mics are enabled
is a runtime configuration of routing, so to me it makes sense also that we can
configure which channel triggers an event, based on our scenario at that time.
Powered by blists - more mailing lists