All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@sirena.org.uk>
To: "Daniel Glöckner" <dg@emlix.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [patch 1/2] alsa: ASoC driver for s6000 I2S	interface
Date: Fri, 27 Mar 2009 16:56:16 +0000	[thread overview]
Message-ID: <20090327165616.GA9314@sirena.org.uk> (raw)
In-Reply-To: <49CD039D.8070302@emlix.com>

On Fri, Mar 27, 2009 at 05:49:33PM +0100, Daniel Glöckner wrote:

> s6000_i2s_start and s6000_i2s_stop are called in s6000_pcm_trigger and
> s6000_i2s_int_sources is called in the interrupt handler.

> s6000_i2s_start can't be called from the dai's trigger callback on playback as
> the data sheet is very explicit about the order of enabling dma and i2s.

> s6000_i2s_stop is called there for consistency. The order on disabling is
> uncritical.

Are these two drivers really separate?  The reason for splitting out the
DMA driver in the normal case is that it is common for CPUs to be able
to use the same DMA driver for multiple interfaces - if that's not the
case then don't feel obligated to split them up too much.

Also note that you can pass data from the I2S driver to the PCM driver
via the dma_data pointer - if you need to pass a little vtable through
there then that's another option.

      reply	other threads:[~2009-03-27 16:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 13:36 [patch 1/2] alsa: ASoC driver for s6000 I2S interface Daniel Glöckner
2009-03-26 13:36 ` [patch 2/2] alsa: s6105 IP camera machine specific ASoC code Daniel Glöckner
2009-03-26 14:26   ` Mark Brown
2009-03-27 16:33     ` Daniel Glöckner
2009-03-27 16:39       ` Mark Brown
2009-03-26 14:15 ` [patch 1/2] alsa: ASoC driver for s6000 I2S interface Mark Brown
2009-03-27 16:09   ` Daniel Glöckner
2009-03-27 16:20     ` Mark Brown
2009-03-27 16:49       ` Daniel Glöckner
2009-03-27 16:56         ` Mark Brown [this message]

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=20090327165616.GA9314@sirena.org.uk \
    --to=broonie@sirena.org.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=dg@emlix.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.