All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: alsa-devel@alsa-project.org, broonie@opensource.wolfsonmicro.com,
	felipe.balbi@nokia.com
Subject: Re: [PATCH 0/2] ASoC: tlv320dac33: small power handling updates
Date: Mon, 17 May 2010 20:35:59 +0100	[thread overview]
Message-ID: <1274124959.3185.8.camel@odin> (raw)
In-Reply-To: <1274095306-24838-1-git-send-email-peter.ujfalusi@nokia.com>

On Mon, 2010-05-17 at 14:21 +0300, Peter Ujfalusi wrote:
> Hello,
> 
> While testing suspend, it has been noticed, that the driver would
> try to power off the codec more than once.
> Since this case handled in the driver, and results no functional
> defect we can lower the noise in the kernel log.
> 
> Also avoid the root cause of the multiple off calls by filtering
> BIAS_OFF request when the codec was already OFF.
> 
> ---
> Felipe Balbi (1):
>   ASoC: tlv320dac33: Use dev_dbg in dac33_hard_power function
> 
> Peter Ujfalusi (1):
>   ASoC: tlv320dac33: Avoid powering off while in BIAS_OFF
> 
>  sound/soc/codecs/tlv320dac33.c |    5 ++++-
>  1 files changed, 4 insertions(+), 1 deletions(-)
> 

Applied.

Thanks

Liam
-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk

      parent reply	other threads:[~2010-05-17 19:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-17 11:21 [PATCH 0/2] ASoC: tlv320dac33: small power handling updates Peter Ujfalusi
2010-05-17 11:21 ` [PATCH 1/2] ASoC: tlv320dac33: Use dev_dbg in dac33_hard_power function Peter Ujfalusi
2010-05-17 11:21 ` [PATCH 2/2] ASoC: tlv320dac33: Avoid powering off while in BIAS_OFF Peter Ujfalusi
2010-05-17 13:54 ` [PATCH 0/2] ASoC: tlv320dac33: small power handling updates Mark Brown
2010-05-17 19:35 ` 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=1274124959.3185.8.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=felipe.balbi@nokia.com \
    --cc=peter.ujfalusi@nokia.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.