[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87y4izkpkv.wl%kuninori.morimoto.gx@renesas.com>
Date: Thu, 2 Jul 2015 07:07:15 +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>,
(Renesas) shiiba <naoya.shiiba.nx@...esas.com>
Subject: Re: [PATCH 0/4][RFC] regmap: add force write option
Hi Mark
Can I have some feedback about these patches ?
> 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/
Powered by blists - more mailing lists