[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151109140225.GA26072@sirena.org.uk>
Date: Mon, 9 Nov 2015 14:02:25 +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 Mon, Nov 09, 2015 at 12:28:39PM +0000, Opensource [Adam Thomson] wrote:
> On November 8, 2015 10:34, Mark Brown wrote:
> > 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.
The general userspace expectation is that the detection is always active
and consistent rather than varying at runtime - runtime variability
might be a bit surprising for it, and even then variability in what is
detected based on other settings is a bit surprising. If the hardware
is that limited I guess it's about all that can be done but I'm still
not clear what the use cases are for configuring the levels (as opposed
ot the routing).
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists