linux-kernel - Re: [PATCH 2/3] regmap: Add API call apply but not register a patch file

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sun, 23 Feb 2014 16:11:59 +0000
From:	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
To:	Mark Brown <broonie@...nel.org>
Cc:	gregkh@...uxfoundation.org, sameo@...ux.intel.com,
	lee.jones@...aro.org, linux-kernel@...r.kernel.org,
	patches@...nsource.wolfsonmicro.com
Subject: Re: [PATCH 2/3] regmap: Add API call apply but not register a
	patch file

On Sat, Feb 22, 2014 at 11:10:48AM +0900, Mark Brown wrote:
> On Fri, Feb 21, 2014 at 07:37:11PM +0000, Charles Keepax wrote:
> > This patch provides a new regmap API call that allows a patch to be
> > applied but not registered with the regmap core. Common code between
> > this and the existing regmap_register_patch function is factored out to
> > reduce duplication.
> 
> This is just regmap_multi_reg_write() I think?  That already exists, the
> theory was that we're going to get an optimised version of that for some
> hardware which can stream things and cut out some overheads though that
> doesn't seem to have materialised yet.

I had missed regmap_multi_reg_write but the difference here is that we
apply cache bypass, and that the cache bypass is only applied whilst the
regmap lock is held. This allows users to be sure that no writes
from other threads will accidentally have the bypass applied to them.

Thanks,
Charles
--
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/