From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
Subject: Re: About snd_dmaengine_pcm_trigger()
Date: Wed, 05 Mar 2014 16:22:38 -0800 (PST)
Message-ID: <87bnxktbug.wl%kuninori.morimoto.gx@gmail.com>
References: <87eh2hql03.wl%kuninori.morimoto.gx@gmail.com>
 <5316D562.3010901@metafoo.de>
 <874n3dqc4j.wl%kuninori.morimoto.gx@gmail.com>
 <5316EC79.4090202@metafoo.de>
Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <alsa-devel-bounces@alsa-project.org>
Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com
 [209.85.220.51])
 by alsa0.perex.cz (Postfix) with ESMTP id 91AB426516E
 for <alsa-devel@alsa-project.org>; Thu,  6 Mar 2014 01:22:40 +0100 (CET)
Received: by mail-pa0-f51.google.com with SMTP id kq14so1845289pab.10
 for <alsa-devel@alsa-project.org>; Wed, 05 Mar 2014 16:22:39 -0800 (PST)
In-Reply-To: <5316EC79.4090202@metafoo.de>
List-Unsubscribe: <http://mailman.alsa-project.org/mailman/options/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>
Errors-To: alsa-devel-bounces@alsa-project.org
Sender: alsa-devel-bounces@alsa-project.org
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>, Simon <horms@verge.net.au>, Mark Brown <broonie@kernel.org>, Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>, Liam Girdwood <lgirdwood@gmail.com>
List-Id: alsa-devel@alsa-project.org


Hi Lars, Mark

> > platform  : for PIO or DMA transfer method
> > component : for DAI configuration = CPU side HW settings etc
> >
> > Is this correct ?
> >
> 
> Yes.

Thank you

> > And about ASoC-like framework, rcar driver needs to control many kind of devices,
> > and it depends on platform which device is used.
> > (each devices have different feature)
> > So, I used ASoC-like framework, but in this case, what should I do ?
> 
> Make them ASoC components ;) I don't know the hardware, but looking at the 
> code it doesn't seem to be that different from other modern host side audio 
> processing units. But one step at a time, first maybe try and see if you can 
> switch over to using the dmaengine PCM helper functions. Then later thing 
> about how this all can be better integrated into the ASoC framework.

OK, I see. will do.
I guess it needs many steps.
OTOH, in reality, I need to work for my business task too.
Thus, actually, I need to add new feature on current rcar driver.
So, My plain is...

 - send new feature patch to ML
 - work for switching to above ASoC framework

Is this acceptable ?

Best regards
---
Kuninori Morimoto