From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Patrick Lai <plai@codeaurora.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: Question about your DSP topic branch
Date: Thu, 17 Mar 2011 11:57:28 +0000 [thread overview]
Message-ID: <20110317115727.GB31411@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4D81B84E.1060607@codeaurora.org>
On Thu, Mar 17, 2011 at 12:29:18AM -0700, Patrick Lai wrote:
> I see a flag "no_codec" defined in struct snd_soc_dai_link. Is that
> flag going to stay or just a temporary workaround?
That's actually not referenced at all at the minute so it's not even a
workaround and should be removed :) . I'd not expect to use that for
this as a lot of the links that use this are something <-> CODEC ones, I
suspect that's an early merged bit of the DSP config propagation stuff
but I'd need to check.
next prev parent reply other threads:[~2011-03-17 11:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D2652C8.7030701@codeaurora.org>
2011-01-25 7:01 ` Question about your DSP topic branch Patrick Lai
2011-01-25 11:51 ` Mark Brown
2011-01-26 6:22 ` Patrick Lai
2011-01-26 11:20 ` Mark Brown
2011-01-27 21:51 ` Patrick Lai
2011-01-31 13:30 ` Mark Brown
2011-03-17 7:29 ` Patrick Lai
2011-03-17 11:57 ` Mark Brown [this message]
2011-01-25 16:46 ` Liam Girdwood
2011-01-27 23:41 ` Patrick Lai
2011-03-15 7:08 ` [alsa-devel] " Patrick Lai
2011-03-15 11:25 ` Mark Brown
2011-03-17 7:21 ` Patrick Lai
2011-03-17 23:58 ` Mark Brown
2011-03-30 20:39 ` Question about your DSP topic Patrick Lai
2011-03-31 6:40 ` Question about your DSP topic branch Patrick Lai
2011-03-31 21:35 ` Liam Girdwood
2011-03-31 21:42 ` Mark Brown
2011-03-31 22:07 ` Patrick Lai
2011-03-31 18:26 ` Question about your DSP topic Liam Girdwood
2011-03-31 20:59 ` Patrick Lai
2011-03-31 21:37 ` Liam Girdwood
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=20110317115727.GB31411@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=plai@codeaurora.org \
/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.