All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Joonyoung Shim <jy0922.shim@samsung.com>
Cc: alsa-devel@alsa-project.org,
	jassi brar <jassisinghbrar@gmail.com>,
	kyungmin.park@samsung.com
Subject: Re: Separate dma driver for cpu_dais
Date: Thu, 18 Feb 2010 09:42:29 +0000	[thread overview]
Message-ID: <20100218094229.GC3315@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <4B7CDA65.6000301@samsung.com>

On Thu, Feb 18, 2010 at 03:12:53PM +0900, Joonyoung Shim wrote:
> On 2/17/2010 7:52 PM, Mark Brown wrote:

> > What modifications are you looking for here?  ASoC doesn't make any

> Thing modified is the active counting of DAI(struct snd_soc_dai) and pcm
> stream(struct snd_soc_pcm_stream). Also, startup() in ops functions of 
> same DAI shouldn't be called several times when the device using same 
> DAI is opened.

Yeah, though it's not 100% clear to me that the multiple calls to
startup() are a bad thing - if the driver does need to coordinate
between multiple possible links then this gives it an opportunity to
handle that.  On the other hand it's likely to be easier for drivers
that do allocations on startup() if there are separate callbacks for
first reference and for each use.

> > can be turned on and off, for example) but these should be things that
> > could be open coded in individual drivers.

> Sorry, what does "be open coded" mean?

Explicitly written in individual drivers rather than being factored out
or otherwise using common code.

  reply	other threads:[~2010-02-18  9:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17  2:39 Separate dma driver for cpu_dais jassi brar
2010-02-17  6:58 ` Joonyoung Shim
2010-02-17  7:24   ` jassi brar
2010-02-17  7:37     ` Joonyoung Shim
2010-02-17 10:52   ` Mark Brown
2010-02-17 12:15     ` jassi brar
2010-02-17 13:14       ` Mark Brown
2010-02-18  2:14         ` jassi brar
2010-02-18  9:35           ` Mark Brown
2010-02-18  9:42             ` jassi brar
2010-02-18  9:52               ` Mark Brown
2010-02-18 10:32                 ` jassi brar
2010-02-18 10:57                   ` Mark Brown
2010-02-18 11:59                     ` jassi brar
2010-02-18 13:10                       ` Mark Brown
2010-02-23  5:45                         ` jassi brar
2010-02-23 10:37                           ` Mark Brown
2010-02-19  9:48                       ` jassi brar
2010-02-19  9:50                         ` Mark Brown
2010-02-18  6:12     ` Joonyoung Shim
2010-02-18  9:42       ` Mark Brown [this message]
2010-02-17 10:42 ` Mark Brown
2010-02-17 12:13   ` jassi brar
2010-02-17 12:42     ` 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=20100218094229.GC3315@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=jy0922.shim@samsung.com \
    --cc=kyungmin.park@samsung.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.