From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: How to specify data format if playback/capture
	were different ?
Date: Tue, 21 May 2013 18:02:45 -0700 (PDT)
Message-ID: <87y5b7ltcd.wl%kuninori.morimoto.gx@renesas.com>
References: <87ppwl3v71.wl%kuninori.morimoto.gx@renesas.com>
 <519B615B.5070409@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-pd0-f182.google.com (mail-pd0-f182.google.com
 [209.85.192.182])
 by alsa0.perex.cz (Postfix) with ESMTP id 254B1261AB7
 for <alsa-devel@alsa-project.org>; Wed, 22 May 2013 03:02:47 +0200 (CEST)
Received: by mail-pd0-f182.google.com with SMTP id g10so1171784pdj.13
 for <alsa-devel@alsa-project.org>; Tue, 21 May 2013 18:02:46 -0700 (PDT)
In-Reply-To: <519B615B.5070409@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>, Mark Brown <broonie@opensource.wolfsonmicro.com>, Liam Girdwood <lgirdwood@gmail.com>, Simon <horms@verge.net.au>, Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
List-Id: alsa-devel@alsa-project.org


Hi Lars

Thank you for your comment

> > But, ak4554 case, data formats are
> >  playback : SND_SOC_DAIFMT_RIGHT_J
> >  capture  : SND_SOC_DAIFMT_LEFT_J
> > and, it can't exchange this data format.
> > 
> > CPU driver should set these information for ak4554 when playback/capture.
> > 
> > Then, how to specify these data format on ALSA SoC ?
> 
> You can add two different DAIs one for playback one for capture. Then you
> can specify the format for each.

I understand, but still 50%.

I'm creating new "cpu" driver now too.
And, fortunately, my current "cpu" can do it as flexibility.
But, my old cpu driver ${LINUX}/sound/soc/sh/fsi.c was this

static struct snd_soc_dai_driver fsi_soc_dai[] = {
	{
		.name			= "fsia-dai",
		.playback = {
			...
		},
		.capture = {
			...
		},
	...

This means, "fsia-dai" is already including "playback" and "capture".
Sould fsi driver be below if "fsi" and "ak4554" are connected ?
Is it normal ?

static struct snd_soc_dai_driver fsi_soc_dai[] = {
	{
		.name			= "fsia-dai",
		.playback = {
			...
		},
		.capture = {
			...
		},
	},
	{
		.name			= "fsia-playback-dai",
		.playback = {
			....
		}
	},
	{
		.name			= "fsia-captrue-dai",
		.capture = {
			....
		}
	}


Best regards
---
Kuninori Morimoto