alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [RFC_iii/iv 1/2] ASoC: Rename dai_link as dev_map
Date: Mon, 1 Nov 2010 13:46:34 -0400	[thread overview]
Message-ID: <20101101174633.GD24814@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20101031201215.9591a614.jhnikula@gmail.com>

On Sun, Oct 31, 2010 at 08:12:15PM +0200, Jarkko Nikula wrote:
> Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:

> > My main thought with this now that I see the change is that it'd be
> > easier and probably clearer to add an explicit list of devices rather
> > than to repurpose the DAI links.  This will probably be simpler since we
> > can avoid things like having to work out if we've seen and initialised a
> > device before when it has multiple DAIs involved.

> My concern was mostly that we end up having somewhat similar struct
> than snd_soc_dai_link and adding pointer to such table in snd_soc_card.

We probably want to be pulling stuff out of the DAI link if anything
(for example, the CODEC is generally going to be implied by the CODEC
DAI).

> But that's not necessary reduncandy at all if it makes cleanier move to
> other cases like codec-codec etc. I'll experiment that in next version.

Please do - I'd rather have a series of small, clear descriptive lists
than a single big list since I think that this will be much clearer and
easier to work with.

      reply	other threads:[~2010-11-01 17:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1288353780-22041-1-git-send-email-jhnikula@gmail.com>
2010-10-29 12:03 ` [RFC_iii/iv 2/2] ASoC: Allow register dailess codecs in machine driver Jarkko Nikula
2010-10-29 21:22 ` [RFC_iii/iv 1/2] ASoC: Rename dai_link as dev_map Mark Brown
2010-10-31 18:12   ` Jarkko Nikula
2010-11-01 17:46     ` 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=20101101174633.GD24814@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jhnikula@gmail.com \
    --cc=lrg@slimlogic.co.uk \
    /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).