[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150421101416.GC22845@sirena.org.uk>
Date: Tue, 21 Apr 2015 11:14:16 +0100
From: Mark Brown <broonie@...nel.org>
To: Sascha Hauer <s.hauer@...gutronix.de>
Cc: Koro Chen <koro.chen@...iatek.com>, robh+dt@...nel.org,
matthias.bgg@...il.com, perex@...ex.cz, tiwai@...e.de,
srv_heupstream@...iatek.com, linux-mediatek@...ts.infradead.org,
galak@...eaurora.org, lgirdwood@...il.com,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, alsa-devel@...a-project.org
Subject: Re: [RESEND RFC PATCH 1/3] ASoC: mediatek: Add binding support for
AFE driver
On Tue, Apr 21, 2015 at 11:49:26AM +0200, Sascha Hauer wrote:
> I think this could be done. I checked the possible connections in the
> crossbar switch and it seems all memory interfaces can be connected with
> all relevant external interfaces. So indeed the memory interfaces could
> be dynamically allocated instead of statically associated to an
> external interface. There are two problems I see: Some memory interfaces
> are limited in the rates they support, they can only do 8k/16k/32k (for
> speech). How can we know such memory interface should be used? Also
> there are two programmable hardware gain blocks which can be inserted to
> the digital audio path using the crossbar switch. There must be some
> mechanism to configure them into different places.
This (particularly the gain controls) sounds like you want to expose the
routing to userspace and use DPCM, the code also seemed to look like it
was a good fit for DPCM.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists