From: Jarkko Nikula <jhnikula@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.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: Sun, 31 Oct 2010 20:12:15 +0200 [thread overview]
Message-ID: <20101031201215.9591a614.jhnikula@gmail.com> (raw)
In-Reply-To: <20101029212249.GJ3921@opensource.wolfsonmicro.com>
On Fri, 29 Oct 2010 14:22:49 -0700
Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
> On Fri, Oct 29, 2010 at 03:02:59PM +0300, Jarkko Nikula wrote:
> > Thus far the struct snd_soc_dai_link is used to tie together platform, codec
> > and cpu dai drivers in a machine driver and all of these devices has been
> > required for a link.
>
> 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.
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.
--
Jarkko
next prev parent reply other threads:[~2010-10-31 18:10 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 [this message]
2010-11-01 17:46 ` 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=20101031201215.9591a614.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.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).