alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: core: Mark regmap CODEC register maps as dirty when suspending
Date: Wed, 12 Sep 2012 17:36:41 +0100	[thread overview]
Message-ID: <1347467801.5312.0.camel@odin> (raw)
In-Reply-To: <1347423794-8606-1-git-send-email-broonie@opensource.wolfsonmicro.com>

On Wed, 2012-09-12 at 12:23 +0800, Mark Brown wrote:
> The core has for a long time had support for marking the register maps of
> devices dirty when suspending so that they are resynced on resume. Also
> implement this feature for CODECs using regmap.
> 
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
>  sound/soc/soc-core.c |    2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/sound/soc/soc-core.c b/sound/soc/soc-core.c
> index 0c7e477..b94ce32 100644
> --- a/sound/soc/soc-core.c
> +++ b/sound/soc/soc-core.c
> @@ -635,6 +635,8 @@ int snd_soc_suspend(struct device *dev)
>  				codec->driver->suspend(codec);
>  				codec->suspended = 1;
>  				codec->cache_sync = 1;
> +				if (codec->using_regmap)
> +					regcache_mark_dirty(codec->control_data);
>  				break;
>  			default:
>  				dev_dbg(codec->dev, "CODEC is on over suspend\n");

Acked-by: Liam Girdwood <lrg@ti.com>

      reply	other threads:[~2012-09-12 16:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12  4:23 [PATCH] ASoC: core: Mark regmap CODEC register maps as dirty when suspending Mark Brown
2012-09-12 16:36 ` 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=1347467801.5312.0.camel@odin \
    --to=lrg@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@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).