linux-kernel - [PATCH 0/4][RFC] regmap: add force write option

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-next>] [day] [month] [year] [list]

Date:	Tue, 16 Jun 2015 08:51:47 +0000
From:	Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
To:	Mark Brown <broonie@...nel.org>
CC:	Linux-Kernel <linux-kernel@...r.kernel.org>,
	Greg KH <gregkh@...uxfoundation.org>,
	shiiba <naoya.shiiba.nx@...esas.com>
Subject: [PATCH 0/4][RFC] regmap: add force write option

Hi Mark

Current _regmap_update_bits() writes data to register if current value and
write value was different. This means it doesn't write data if the value was
same as current value.
But, some device needs to write data even though it was same value.

This RFC patch-set adds new "force_write" option on _regmap_update_bits()
for this issue, but it focuses only 1 regmap write function at this point,
because there are many regmap_xxx_write_yyy() functions.
I can care all of regmap_xxx_write_yyy() functions in formal patch-set if
this RFC patch idea was OK.

What do you think about this idea ?

Kuninori Morimoto (4):
      regmap: add force_write option on _regmap_update_bits()
      regmap: add regmap_write_bits()
      regmap: add regmap_fields_force_write()
      ASoC: rsnd: gen: add rsnd_force_write()

 drivers/base/regmap/regmap.c | 51 +++++++++++++++++++++++++++++++++++++++++++--------
 include/linux/regmap.h       | 11 +++++++++++
 sound/soc/sh/rcar/gen.c      | 16 ++++++++++++++++
 sound/soc/sh/rcar/rsnd.h     |  4 ++++
 4 files changed, 74 insertions(+), 8 deletions(-)

Best regards
---
Kuninori Morimoto
--
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/