linux-kernel - Re: [PATCH 3/3] mfd: arizona: Use new regmap features for manual register patch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140225100216.GA13246@lee--X1>
Date:	Tue, 25 Feb 2014 10:02:16 +0000
From:	Lee Jones <lee.jones@...aro.org>
To:	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
Cc:	broonie@...nel.org, gregkh@...uxfoundation.org,
	sameo@...ux.intel.com, linux-kernel@...r.kernel.org,
	patches@...nsource.wolfsonmicro.com
Subject: Re: [PATCH 3/3] mfd: arizona: Use new regmap features for manual
 register patch

> > > 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@...nsource.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.

It's a good idea to let us know about any inter-patch dependencies, so
we may act accordingly. I'll remove this from my -next branch for now.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/