From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: broonie@kernel.org, gregkh@linuxfoundation.org,
sameo@linux.intel.com, linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 3/3] mfd: arizona: Use new regmap features for manual register patch
Date: Tue, 25 Feb 2014 09:37:23 +0000 [thread overview]
Message-ID: <20140225093723.GE5438@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20140224161042.GF15847@lee--X1>
On Mon, Feb 24, 2014 at 04:10:42PM +0000, Lee Jones wrote:
> > On the wm5102 the register patches are applied manually, rather than by
> > the regmap core. This application is wrapped in calls to
> > regcache_cache_bypass. However, this is dangerous as other threads may
> > be accessing the hardware at the same time as the pm_runtime operations
> > and if they do so during the period whilst cache_bypass is enabled those
> > writes will miss the cache when they shouldn't.
> >
> > Apply the register patch using the new regmap_apply_patch function to
> > avoid this problem. Also remove the call to regcache_cache_bypass from
> > the hardware patch application as it is unneeded there and creates a
> > similar window for writes to miss the cache.
> >
> > Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> > ---
> > drivers/mfd/arizona-core.c | 4 ----
> > drivers/mfd/wm5102-tables.c | 19 ++-----------------
> > 2 files changed, 2 insertions(+), 21 deletions(-)
>
> Applied, thanks.
Apologies this patch depends on the previous patch I am still
working Mark's comments for. So this can't really be applied at
the moment.
Thanks,
Charles
next prev parent reply other threads:[~2014-02-25 9:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 19:37 [PATCH 1/3] regmap: Check stride of register patch as we register it Charles Keepax
2014-02-21 19:37 ` [PATCH 2/3] regmap: Add API call apply but not register a patch file Charles Keepax
2014-02-22 2:10 ` Mark Brown
2014-02-23 16:11 ` Charles Keepax
2014-02-24 1:24 ` Mark Brown
2014-02-21 19:37 ` [PATCH 3/3] mfd: arizona: Use new regmap features for manual register patch Charles Keepax
2014-02-24 16:10 ` Lee Jones
2014-02-25 9:37 ` Charles Keepax [this message]
2014-02-25 10:02 ` Lee Jones
2014-02-22 2:15 ` [PATCH 1/3] regmap: Check stride of register patch as we register it 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=20140225093723.GE5438@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.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