From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 4/6] compress: add API header and driver
 header	files
Date: Mon, 5 Dec 2011 14:19:05 +0000
Message-ID: <20111205141905.GR11150@opensource.wolfsonmicro.com>
References: <1314943585-11670-1-git-send-email-vinod.koul@linux.intel.com>
	<1321951920-4363-5-git-send-email-vinod.koul@linux.intel.com>
	<3CA6C6D9F70D314CA34352990B57DA1507CCA82D17@bgsmsx502.gar.corp.intel.com>
	<000301ccb124$72a53370$57ef9a50$@bossart@linux.intel.com>
	<3CA6C6D9F70D314CA34352990B57DA1507CCAD7952@bgsmsx502.gar.corp.intel.com>
	<000001ccb358$2b9e4b70$82dae250$@bossart@linux.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <alsa-devel-bounces@alsa-project.org>
Received: from opensource.wolfsonmicro.com (opensource.wolfsonmicro.com
	[80.75.67.52]) by alsa0.perex.cz (Postfix) with ESMTP id D1EA92442C
	for <alsa-devel@alsa-project.org>; Mon,  5 Dec 2011 15:19:07 +0100 (CET)
Content-Disposition: inline
In-Reply-To: <000001ccb358$2b9e4b70$82dae250$@bossart@linux.intel.com>
List-Unsubscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
	<mailto:alsa-devel-request@alsa-project.org?subject=unsubscribe>
List-Archive: <http://mailman.alsa-project.org/pipermail/alsa-devel>
List-Post: <mailto:alsa-devel@alsa-project.org>
List-Help: <mailto:alsa-devel-request@alsa-project.org?subject=help>
List-Subscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
	<mailto:alsa-devel-request@alsa-project.org?subject=subscribe>
Sender: alsa-devel-bounces@alsa-project.org
Errors-To: alsa-devel-bounces@alsa-project.org
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: tiwai@suse.de, 'Vinod Koul' <vinod.koul@linux.intel.com>, lrg@ti.com, alsa-devel@alsa-project.org, "Nallasellan,
	Singaravelan" <singaravelan.nallasellan@intel.com>
List-Id: alsa-devel@alsa-project.org

On Mon, Dec 05, 2011 at 08:14:13AM -0600, Pierre-Louis Bossart wrote:

> The answer has already been provided. I agree with Mark there's no reason
> why this API would need to provide resource management capabilities, it'd
> need to be handled with a separate interface addressing PCM and effects as
> well. In the mean time user-space can put product-specific restrictions on
> concurrent decoding.

Or implement graceful fallback to the CPU if it can't set up an
offloaded stream.