From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: user space control app driver interface for sound soc Date: Thu, 30 Sep 2010 13:31:19 -0700 Message-ID: <20100930203118.GA4175@opensource.wolfsonmicro.com> References: <20100929033757.GB29975@opensource.wolfsonmicro.com> <20100929221826.GC31934@opensource.wolfsonmicro.com> <20100930005850.GB4517@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 ABBBC103967 for ; Thu, 30 Sep 2010 22:31:03 +0200 (CEST) Content-Disposition: inline In-Reply-To: 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: Peter Hsiang Cc: "alsa-devel@alsa-project.org" List-Id: alsa-devel@alsa-project.org On Thu, Sep 30, 2010 at 10:23:54AM -0700, Peter Hsiang wrote: > If I want to build an audio user space app to perform things like > transferring large blocks of data to the sound soc codec > using I2C, what is the best kernel driver interface to use > for this purpose? Add file interface (read/write/ioctl) in the > sound soc codec driver, or does ALSA already have this? > The soc codec driver needs to co-exist with this mechanism. This depends on what's idiomatic for the data you need to download - what is the data?