From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: sta32x: Write the register default value to cache for reserved registers
Date: Thu, 13 Oct 2011 11:51:58 +0100 [thread overview]
Message-ID: <20111013105158.GD5193@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1318489051.2857.3.camel@phoenix>
On Thu, Oct 13, 2011 at 02:57:31PM +0800, Axel Lin wrote:
> Chip documentation explicitly requires that the reset values
> of reserved register bits are left untouched.
Applied, but this seems really wierd - shouldn't we just be getting this
stuff from the cache defaults? Why do we explicitly need to write to
the cache?
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org, Liam Girdwood <lrg@ti.com>,
Johannes Stezenbach <js@sig21.net>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: sta32x: Write the register default value to cache for reserved registers
Date: Thu, 13 Oct 2011 11:51:58 +0100 [thread overview]
Message-ID: <20111013105158.GD5193@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1318489051.2857.3.camel@phoenix>
On Thu, Oct 13, 2011 at 02:57:31PM +0800, Axel Lin wrote:
> Chip documentation explicitly requires that the reset values
> of reserved register bits are left untouched.
Applied, but this seems really wierd - shouldn't we just be getting this
stuff from the cache defaults? Why do we explicitly need to write to
the cache?
next prev parent reply other threads:[~2011-10-13 10:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 6:40 [PATCH] ASoC: sta32x: Set reg_cache_default to sta32x_regs Axel Lin
2011-10-13 6:57 ` [PATCH] ASoC: sta32x: Write the register default value to cache for reserved registers Axel Lin
2011-10-13 6:57 ` Axel Lin
2011-10-13 10:51 ` Mark Brown [this message]
2011-10-13 10:51 ` Mark Brown
2011-10-13 10:51 ` [PATCH] ASoC: sta32x: Set reg_cache_default to sta32x_regs Mark Brown
2011-10-13 10:51 ` 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=20111013105158.GD5193@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=axel.lin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@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.