From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [Device-drivers-devel] [PATCH] Add driver for Analog Devices ADAU1701 SigmaDSP Date: Tue, 19 Apr 2011 09:06:29 +0100 Message-ID: <20110419080629.GA16357@opensource.wolfsonmicro.com> References: <1299460302-15392-1-git-send-email-cliff.cai@analog.com> <20110307114142.GB13471@opensource.wolfsonmicro.com> <20110307121502.GG13471@opensource.wolfsonmicro.com> <20110307145931.GK13471@opensource.wolfsonmicro.com> <20110418171505.4b1699f3@queued.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from opensource2.wolfsonmicro.com (opensource.wolfsonmicro.com [80.75.67.52]) by alsa0.perex.cz (Postfix) with ESMTP id 0575D243F5 for ; Tue, 19 Apr 2011 10:06:23 +0200 (CEST) Content-Disposition: inline In-Reply-To: <20110418171505.4b1699f3@queued.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Andres Salomon Cc: cliff.cai@analog.com, Mike Frysinger , alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org, device-drivers-devel@blackfin.uclinux.org, akpm@linux-foundation.org, lrg@slimlogic.co.uk List-Id: alsa-devel@alsa-project.org On Mon, Apr 18, 2011 at 05:15:05PM -0700, Andres Salomon wrote: > Mark Brown wrote: > > Given the number of people looking at this from various angles I'd > > expect to see some sort of progress this year (probably in the next > > quater or so), but obviously no guarantees. > Out of curiosity, has any progress been made on this? No, it's only been a month. > What would actually cause the firmware to change? Would the userspace > application that's currently driving the codec know that it needs to > load a new firmware, or will there be multiple applications potentially > interacting with the codec (with only one driving it, and another > deciding that the firmware should change)? Clearly something in userspace will need to be able to do this. > One can imagine two different types of APIs depending upon the answers > to those questions. If the application driving the codec is also > changing the firmware, a simple 'echo new_firmware_name.bin > > /sys/.../filter_coeff' (or equivalent ALSA function) Using sysfs isn't going to fly for all the reasons discussed upthread - it's not enumerable and it's not going to cope with large coefficient sets. > However, if multiple applications are going to be interacting with > the codec, I'd imagine we'd need something more complex; perhaps a hook > in snd_soc_dai_ops that's called anytime stream state changes? That Using the ops isn't going to work as there's no reason a coefficient set has to be associated with a DAI.