From: Liam Girdwood <lrg@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] ASoC: dapm: Ensure power gets managed for line widgets
Date: Mon, 16 Apr 2012 16:01:08 +0100 [thread overview]
Message-ID: <1334588468.2255.3.camel@odin> (raw)
In-Reply-To: <1334248206-17959-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Thu, 2012-04-12 at 17:30 +0100, Mark Brown wrote:
> Line widgets had not been included in either the power up or power down
> sequences so if a widget had an event associated with it that event would
> never be run. Fix this minimally by adding them to the sequences, we
> should probably be doing away with the specific widget types as they all
> have the same priority anyway.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Acked-by: Liam Girdwood <lrg@ti.com>
prev parent reply other threads:[~2012-04-16 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 16:30 [PATCH] ASoC: dapm: Ensure power gets managed for line widgets Mark Brown
2012-04-16 15:01 ` Liam Girdwood [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=1334588468.2255.3.camel@odin \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=patches@opensource.wolfsonmicro.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).