All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Barry Song <21cnbao@gmail.com>
Cc: uclinux-dist-devel@blackfin.uclinux.org, "Cai,
	Cliff" <Cliff.Cai@analog.com>,
	alsa-devel@alsa-project.org,
	Mike Frysinger <vapier.adi@gmail.com>
Subject: Re: dev_* output functions and ASoC codecs
Date: Mon, 12 Oct 2009 15:20:18 +0100	[thread overview]
Message-ID: <20091012142018.GA18283@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <3c17e3570910120620g7e65f87ekeb854c373375b7a3@mail.gmail.com>

On Mon, Oct 12, 2009 at 09:20:18PM +0800, Barry Song wrote:

> Thanks a lot. Fortunately, You parsed my meaning well. I just want to
> say it seems not too economic to have arrays with almost same members
> while CPU interfaces and codecs are same for all dai_links. dai[0] and
> dai[1] in array are just same.  It seems that will make more sense if

The current plan is to allow a dev_name plus DAI index instead of the
pointer to be used to establish the link, though I can't guarantee that
particular approach until it's implemented.

  reply	other threads:[~2009-10-12 14:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06  0:18 dev_* output functions and ASoC codecs Mike Frysinger
2009-10-06 10:20 ` Mark Brown
2009-10-12  2:26   ` Barry Song
2009-10-12  9:36     ` Mark Brown
2009-10-12 10:34       ` Barry Song
2009-10-12 10:48         ` Mark Brown
2009-10-12 13:20           ` Barry Song
2009-10-12 14:20             ` Mark Brown [this message]
2009-10-13 10:09               ` Barry Song
2009-10-13 10:14                 ` Mark Brown
2009-10-20  5:27                   ` Barry Song
2009-10-20  9:52                     ` 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=20091012142018.GA18283@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=21cnbao@gmail.com \
    --cc=Cliff.Cai@analog.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=uclinux-dist-devel@blackfin.uclinux.org \
    --cc=vapier.adi@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.