All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
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>
Subject: Re: How to specify data format if playback/capture were different ?
Date: Tue, 21 May 2013 18:02:45 -0700 (PDT)	[thread overview]
Message-ID: <87y5b7ltcd.wl%kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <519B615B.5070409@metafoo.de>


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

  reply	other threads:[~2013-05-22  1:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21  2:47 How to specify data format if playback/capture were different ? Kuninori Morimoto
2013-05-21 11:58 ` Lars-Peter Clausen
2013-05-22  1:02   ` Kuninori Morimoto [this message]
2013-05-22  1:12     ` Kuninori Morimoto
2013-05-22  8:43       ` Lars-Peter Clausen
2013-05-22  8:54         ` Kuninori Morimoto
2013-05-22 11:41           ` Lars-Peter Clausen
2013-05-24  3:18             ` Kuninori Morimoto
2013-05-25 20:03               ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y5b7ltcd.wl%kuninori.morimoto.gx@renesas.com \
    --to=kuninori.morimoto.gx@renesas.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=horms@verge.net.au \
    --cc=kuninori.morimoto.gx@gmail.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.