From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [PATCH 2/7] ASoC: DAPM: Pass snd_dapm_soc_update as parameter Date: Thu, 28 Apr 2011 23:23:15 +0100 Message-ID: <20110428222315.GA19741@opensource.wolfsonmicro.com> References: <1304009173-5786-1-git-send-email-lars@metafoo.de> <1304009173-5786-2-git-send-email-lars@metafoo.de> <20110428194054.GB16837@opensource.wolfsonmicro.com> <4DB9D06C.5090006@metafoo.de> <20110428205827.GA18350@opensource.wolfsonmicro.com> <4DB9DB16.1060507@metafoo.de> <20110428214817.GA19535@opensource.wolfsonmicro.com> <4DB9E454.3060903@metafoo.de> <20110428221800.GC19535@opensource.wolfsonmicro.com> 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 E075D2442B for ; Fri, 29 Apr 2011 00:23:08 +0200 (CEST) Content-Disposition: inline In-Reply-To: <20110428221800.GC19535@opensource.wolfsonmicro.com> 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: Lars-Peter Clausen Cc: alsa-devel@alsa-project.org, Liam Girdwood List-Id: alsa-devel@alsa-project.org On Thu, Apr 28, 2011 at 11:18:00PM +0100, Mark Brown wrote: > On Fri, Apr 29, 2011 at 12:04:04AM +0200, Lars-Peter Clausen wrote: > > On 04/28/2011 11:48 PM, Mark Brown wrote: > > > Moving to the card doesn't seem helpful, while we're currently doing one > > > update at once it's not immediately obvious that we want to keep doing > > > that indefinitely. > > But keeping it in the dapm context would limit us to one update per context > > which doesn't seem very sustainable either. > Though for global state changes like this that's pretty much irrelevant > as we need to walk the entire graph at once. BTW, this means that my above comment was too hasty; I can't actually see a situation where we'd ever want to have multiple updates in flight. Though I also don't immediately see a need to move as the update gets applied to a specific context anyway and it seems nicer to just stop using the stream events for anything other than the integration with the CPU DMA.