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>
Subject: Re: [PATCH v2 0/9] ASoC: OMAP machine driver cleanups
Date: Mon, 10 Oct 2011 16:18:24 +0100 [thread overview]
Message-ID: <20111010151824.GA9895@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1318250056-26437-1-git-send-email-peter.ujfalusi@ti.com>
On Mon, Oct 10, 2011 at 03:34:07PM +0300, Peter Ujfalusi wrote:
> Some cleanups for the OMAP ASoC machine drivers:
> - do not call soc_dapm_sync from dai_link->init callback since it is useless
> - Convert drivers to use table based DAPM initialization
> - Remove dapm_enable_pin calls from dai_link->init callback since pins are
> enabled by default
Applied all, thanks.
prev parent reply other threads:[~2011-10-10 15:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 12:34 [PATCH v2 0/9] ASoC: OMAP machine driver cleanups Peter Ujfalusi
2011-10-10 12:34 ` [PATCH v2 1/9] ASoC: OMAP machines: Remove soc_dapm_sync() call from init Peter Ujfalusi
2011-10-10 12:34 ` [PATCH v2 2/9] ASoC: am3517evm: Let core to deal with the DAPM widgets Peter Ujfalusi
2011-10-10 12:34 ` [PATCH v2 3/9] ASoC: n810: Let the core to register DAPM widgets/routes and controls Peter Ujfalusi
2011-10-10 12:34 ` [PATCH v2 4/9] ASoC: osk5912: Let core to deal with the DAPM widgets Peter Ujfalusi
2011-10-10 12:34 ` [PATCH v2 5/9] ASoC: sdp3430: " Peter Ujfalusi
2011-10-10 12:34 ` [PATCH v2 6/9] ASoC: zoom2: " Peter Ujfalusi
2011-10-10 12:34 ` [PATCH v2 7/9] ASoC: zoom2: No need to call dapm_pin_enable at init time Peter Ujfalusi
2011-10-10 12:34 ` [PATCH v2 8/9] ASoC: sdp4430: Let core to deal with the DAPM widgets Peter Ujfalusi
2011-10-10 12:34 ` [PATCH v2 9/9] ASoC: sdp4430: No need to call dapm_pin_enable at init time Peter Ujfalusi
2011-10-10 15:18 ` 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=20111010151824.GA9895@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@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 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.