Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Kevin Cernekee <cernekee@chromium.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	dgreid@chromium.org, Andrew Bresticker <abrestic@chromium.org>,
	Olof Johansson <olofj@chromium.org>,
	alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH 2/3] ASoC: tas571x: New driver for TI TAS571x power amplifiers
Date: Fri, 24 Apr 2015 17:50:38 +0100	[thread overview]
Message-ID: <20150424165038.GS22845@sirena.org.uk> (raw)
In-Reply-To: <CAJzqFtZ3wMHHoAesUZws0b4csArsjeZTKeB7FbU7OSSbmCT1nA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 673 bytes --]

On Fri, Apr 24, 2015 at 06:52:01AM -0700, Kevin Cernekee wrote:
> On Fri, Apr 24, 2015 at 2:28 AM, Mark Brown <broonie@kernel.org> wrote:

> > Do you need to work around it?  If the register map is being perserved
> > you don't need to sync so just don't do it - it's just that the normal
> > expectation would be that power down would cause the register map to be
> > reset.

> How do I tell regcache to write out any updates that happened while
> the hardware was inaccessible?  I see that regmap->cache_dirty is 1,
> but nothing flushes it automatically when exiting cache_only mode.

Oh, I see.  A sync will be required, yes.  Probably resetting the device
is easiest.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-04-24 16:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15 21:42 [PATCH 1/3] ASoC: tas571x: Add DT binding document Kevin Cernekee
2015-04-15 21:42 ` [PATCH 2/3] ASoC: tas571x: New driver for TI TAS571x power amplifiers Kevin Cernekee
     [not found]   ` <1429134141-17924-2-git-send-email-cernekee-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2015-04-16 12:57     ` [alsa-devel] " Lars-Peter Clausen
     [not found]       ` <552FB1CD.3040401-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>
2015-04-18 11:39         ` Mark Brown
2015-04-20 20:56       ` Kevin Cernekee
2015-04-20 21:14         ` Mark Brown
2015-04-18 11:36   ` Mark Brown
     [not found]     ` <20150418113632.GE26185-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-04-18 16:16       ` Kevin Cernekee
2015-04-18 17:11         ` Mark Brown
2015-04-18 20:07           ` Kevin Cernekee
     [not found]             ` <CAJzqFtZ97FjzDpgbSJbCkqNGnQx_QiGrzY1v1zV+croAL6_=qw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-20 12:21               ` Mark Brown
     [not found]                 ` <20150420122129.GC14892-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-04-20 15:12                   ` Kevin Cernekee
2015-04-20 16:05                     ` Andrew Bresticker
     [not found]                     ` <CAJzqFtY3-jYTS-NmAE4UtsD+VXZHBUJUVuVQ=X4htB1akCThMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-20 20:14                       ` Mark Brown
     [not found]         ` <CAJzqFtYVd+jHesoNnG47ftoK9SWYUmXwDXpf2==s3Rv1ewpsYg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-24  0:47           ` Kevin Cernekee
2015-04-24  9:28             ` Mark Brown
2015-04-24 13:52               ` Kevin Cernekee
2015-04-24 16:50                 ` Mark Brown [this message]
     [not found] ` <1429134141-17924-1-git-send-email-cernekee-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2015-04-15 21:42   ` [PATCH 3/3] MAINTAINERS: Add entry for tas571x ASoC codec driver Kevin Cernekee
2015-04-18 11:16 ` [PATCH 1/3] ASoC: tas571x: Add DT binding document Mark Brown
     [not found]   ` <20150418111622.GD26185-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-04-20 21:16     ` Kevin Cernekee
2015-04-20 21:18   ` Kevin Cernekee
2015-04-20 22:03     ` Mark Brown
2015-04-20 22:48       ` Kevin Cernekee
     [not found]         ` <CAJzqFtbseDe8c19ZpZjw3y72-+eO1+Zcq7D+DC=0G5_LbimRJg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-21 16:45           ` 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=20150424165038.GS22845@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=abrestic@chromium.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=cernekee@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dgreid@chromium.org \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olofj@chromium.org \
    /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