From: Mark Brown <broonie@kernel.org>
To: "Opensource [Adam Thomson]" <Adam.Thomson.Opensource@diasemi.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>,
Support Opensource <Support.Opensource@diasemi.com>,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Kumar Gala <galak@codeaurora.org>
Subject: Re: [PATCH 2/2] ASoC: codecs: Add da7218 codec driver
Date: Sun, 8 Nov 2015 10:34:29 +0000 [thread overview]
Message-ID: <20151108103429.GC6746@sirena.org.uk> (raw)
In-Reply-To: <2E89032DDAA8B9408CB92943514A0337D460CAAD@SW-EX-MBX01.diasemi.com>
[-- Attachment #1.1: Type: text/plain, Size: 467 bytes --]
On Fri, Nov 06, 2015 at 01:17:28PM +0000, Opensource [Adam Thomson] wrote:
> On November 6, 2015 11:55, 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?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-11-08 10:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 10:43 [PATCH 0/2] ASoC: Add support for DA7217 and DA7218 audio codecs Adam Thomson
2015-11-05 10:43 ` [PATCH 1/2] ASoC: da7218: Add bindings documentation for DA7218 audio codec Adam Thomson
2015-11-05 14:58 ` Mark Brown
2015-11-05 17:59 ` Opensource [Adam Thomson]
2015-11-06 10:30 ` Mark Brown
2015-11-05 10:43 ` [PATCH 2/2] ASoC: codecs: Add da7218 codec driver Adam Thomson
2015-11-05 15:27 ` Mark Brown
2015-11-06 11:11 ` Opensource [Adam Thomson]
[not found] ` <2E89032DDAA8B9408CB92943514A0337D460CA0C-68WUHU125fLLPO1uwJ3ImwLouzNaz+3S@public.gmane.org>
2015-11-06 11:21 ` Mark Brown
2015-11-06 11:53 ` Opensource [Adam Thomson]
2015-11-06 11:54 ` Mark Brown
[not found] ` <20151106115451.GG18409-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-11-06 13:17 ` Opensource [Adam Thomson]
2015-11-08 10:34 ` Mark Brown [this message]
2015-11-09 12:28 ` Opensource [Adam Thomson]
[not found] ` <2E89032DDAA8B9408CB92943514A0337D460CC6C-68WUHU125fLLPO1uwJ3ImwLouzNaz+3S@public.gmane.org>
2015-11-09 14:02 ` Mark Brown
2015-11-10 13:55 ` Opensource [Adam Thomson]
2015-11-10 14:15 ` Mark Brown
2015-11-10 14:24 ` Opensource [Adam Thomson]
2015-11-10 15:44 ` Mark Brown
2015-11-10 16:21 ` Opensource [Adam Thomson]
[not found] ` <2E89032DDAA8B9408CB92943514A0337D460CF5D-68WUHU125fLLPO1uwJ3ImwLouzNaz+3S@public.gmane.org>
2015-11-10 16:42 ` Mark Brown
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=20151108103429.GC6746@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Adam.Thomson.Opensource@diasemi.com \
--cc=Support.Opensource@diasemi.com \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--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).