From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>,
Misael Lopez Cruz <misael.lopez@ti.com>
Subject: Re: [PATCH 1/4] ASoC: omap-abe-twl6040: Keep only one snd_soc_dai_link structure
Date: Tue, 8 May 2012 16:52:55 +0100 [thread overview]
Message-ID: <20120508155255.GB15893@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1336479314-27766-2-git-send-email-peter.ujfalusi@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 335 bytes --]
On Tue, May 08, 2012 at 03:15:11PM +0300, Peter Ujfalusi wrote:
> There is no need to have two snd_soc_dai_link structure for the two setup
> the machine driver supports.
> We can just tell core to register only the first link if the DMIC link is
> not in use on the device.
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-05-08 15:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 12:15 [PATCH 0/4] omap-abe-twl6040: Device tree support Peter Ujfalusi
2012-05-08 12:15 ` [PATCH 1/4] ASoC: omap-abe-twl6040: Keep only one snd_soc_dai_link structure Peter Ujfalusi
2012-05-08 15:52 ` Mark Brown [this message]
2012-05-08 12:15 ` [PATCH 2/4] ASoC: omap-abe-twl6040: Move Digital Mic widget into dapm table Peter Ujfalusi
2012-05-08 18:30 ` Mark Brown
2012-05-08 12:15 ` [PATCH 3/4] ASoC: omap-abe-twl6040: Introduce driver data for runtime parameters Peter Ujfalusi
2012-05-08 18:31 ` Mark Brown
2012-05-08 12:15 ` [PATCH 4/4] ASoC: omap-abe-twl6040: Add device tree support Peter Ujfalusi
2012-05-08 13:59 ` Mark Brown
2012-05-09 11:45 ` Peter Ujfalusi
2012-05-09 15:59 ` 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=20120508155255.GB15893@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=misael.lopez@ti.com \
--cc=peter.ujfalusi@ti.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 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).