alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Jean-Francois Moine <moinejf@free.fr>
To: Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>, Simon <horms@verge.net.au>,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH 0/10] ASoC: rsnd: add SRC support
Date: Tue, 7 Jan 2014 10:21:40 +0100	[thread overview]
Message-ID: <20140107102140.08be6cdd@armhf> (raw)
In-Reply-To: <87wqic4p79.wl%kuninori.morimoto.gx@gmail.com>

On Mon, 06 Jan 2014 16:21:01 -0800 (PST)
Kuninori Morimoto <kuninori.morimoto.gx@gmail.com> wrote:

> > > Thank you for your help.
> > > I see, I will start moving it, but I need sample code for it.
> > > Who is using DPCM ?
> > 
> > Nobody in tree unfortunately.  The TI OMAP and Qualcomm production
> > kernels use it as do some of the newer Intel Haswell chips but all of
> > that is out of tree.  There's also the work Russell has been doing for
> > Kirkwood but I don't think he posted the finished version to the list
> > yet (he's waiting for some fixes from Liam which will hopefully come
> > soon).
> 
> Hmm... OK I understood.
> Do you think it is possible to get these out-of-tree codes
> from somewhere/somehow ?
> I can work for DPCM support for our driver,
> but it is very difficult for me without sample code...
> 
> If I could get sample code, and I finished my current task,
> I will start DPCM support. is it OK ?

Kuninori,

Last month I tried to use DPCM in the Cubox (kirkwood audio + nxp
tda998x HDMI transmitter and S/PDIF), and, as your simple-card was not
easy to extend, I proposed an other way to describe a DPCM audio system
in DT:

http://mailman.alsa-project.org/pipermail/alsa-devel/2013-December/070594.html

and also:

http://mailman.alsa-project.org/pipermail/alsa-devel/2014-January/070634.html

In fact, DPCM just needs many DAI links, and a flag 'front-end' /
'back-end':

http://mailman.alsa-project.org/pipermail/alsa-devel/2014-January/070623.html

Actually, I added many DAI links to your simple-card and I am waiting
for Xiubo's patches to be applied before proposing mine.

This will make the Cubox audio system work by selecting the I2S or
S/PDIF PCM, but it will not be DPCM. The reason is that, with the
actual DPCM, the sample rates and formats are the ones of the
front-end, and not the subset of the ones of the DAIs in the sound
route. I explained this problem in:

http://mailman.alsa-project.org/pipermail/alsa-devel/2013-December/070585.html

and it appears that some development is needed in the sound core to
handle this Cubox case.

Coming back to a DPCM example, apart from adding the 'front-end' and
'back-end' flags in the DAI links, the changes were:

- add the global system playback DAI in the audio controller.

  This DAI is the audio entry point (front-end). On audio open, the
  back-end DAIs are searched and started (snd_pcm_open). If there was a
  platform declared in the associated DAI links, the DMA open would be
  called many times, so

- don't set a platform pointer in the back-end DAI links.

That's all.

If you want more information, I may send you the patch I did for DPCM
in the audio controller (kirkwood-i2s.c).

-- 
Ken ar c'hentañ	|	      ** Breizh ha Linux atav! **
Jef		|		http://moinejf.free.fr/
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2014-01-07  9:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20  3:25 [PATCH 0/10] ASoC: rsnd: add SRC support Kuninori Morimoto
2013-12-20  3:26 ` [PATCH 01/10] ASoC: rsnd: add rsnd_adg_set_ssi_clk() and cleanup adg Kuninori Morimoto
2013-12-20  3:26 ` [PATCH 02/10] ASoC: rsnd: tidyup ssi comment Kuninori Morimoto
2013-12-20  3:27 ` [PATCH 03/10] ASoC: rsnd: tidyup register naming Kuninori Morimoto
2013-12-20  3:27 ` [PATCH 04/10] ASoC: rsnd: make sure variable name for 44.1kHz/48kHz Kuninori Morimoto
2013-12-20  3:27 ` [PATCH 05/10] ASoC: rsnd: route setting is needed only Gen1 Kuninori Morimoto
2013-12-20  3:28 ` [PATCH 07/10] ASoC: rsnd: add rsnd_scu_transfer_start() Kuninori Morimoto
2013-12-20  3:28 ` [PATCH 06/10] ASoC: rsnd: INT_ENABLE is needed only Gen2 Kuninori Morimoto
2013-12-20  3:28 ` [PATCH 08/10] ASoC: rsnd: scu cleanup: add rsnd_scu_rate_ctrl() Kuninori Morimoto
2013-12-20  3:28 ` [PATCH 09/10] ASoC: rsnd: tidyup rsnd_ssi_master_clk_start() parameter Kuninori Morimoto
2013-12-20  3:28 ` [PATCH 10/10] ASoC: rsnd: add SRC (Sampling Rate Converter) support Kuninori Morimoto
2013-12-31 13:36 ` [PATCH 0/10] ASoC: rsnd: add SRC support Mark Brown
2014-01-06  5:29   ` Kuninori Morimoto
2014-01-06 15:23     ` Mark Brown
2014-01-07  0:21       ` Kuninori Morimoto
2014-01-07  9:21         ` Jean-Francois Moine [this message]
2014-01-07 11:22         ` 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=20140107102140.08be6cdd@armhf \
    --to=moinejf@free.fr \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).