All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ziv Haziz <Ziv.Haziz@dspg.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: adding an external dsp under soc-dsp framework
Date: Wed, 8 Aug 2012 11:59:20 +0100	[thread overview]
Message-ID: <20120808105919.GJ16861@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <FC1850374E3CB245B9E97002380578E002221820@ILMAIL01.dspg.com>

On Wed, Aug 08, 2012 at 11:21:20AM +0300, Ziv Haziz wrote:

> >I n that case what you're saying above with a DAI link is exactly what
> > you're supposed to do, I don't see any structural problem here?

> Creating two dai links will create two separated devices which must be
> open for setting configurations, but the dsp-codec dai cannot be started
> (or I will get an  error). This means changing the codec driver to
> enable everything not from trigger callback.

> Is it possible to have a dai link without a platform for data transfer?
> I saw in the plumbers agenda you are going to talk on codec-codec
> interface - do you have any preliminary suggestion?

This is already supported in mainline, look at littlemill for one
example user.

Alternatively for older kernels you can easily support this from
userspace by just not starting the DMA, this has been deployed for some
considerable time on many systems (OpenMoko is one long standing
mainline example).

  parent reply	other threads:[~2012-08-08 10:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <FC1850374E3CB245B9E97002380578E0022216D4@ILMAIL01.dspg.com>
2012-08-06 15:48 ` adding an external dsp under soc-dsp framework Mark Brown
2012-08-06 18:43   ` ziv haziz
2012-08-07 14:09     ` Mark Brown
     [not found]       ` <FC1850374E3CB245B9E97002380578E002221820@ILMAIL01.dspg.com>
2012-08-08 10:59         ` Mark Brown [this message]
     [not found]           ` <FC1850374E3CB245B9E97002380578E00222188A@ILMAIL01.dspg.com>
2012-08-09 10:57             ` Mark Brown
2012-08-06 12:53 ziv haziz
2012-08-06 14:39 ` 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=20120808105919.GJ16861@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=Ziv.Haziz@dspg.com \
    --cc=alsa-devel@alsa-project.org \
    /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.