From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752526AbbGBHqz (ORCPT ); Thu, 2 Jul 2015 03:46:55 -0400 Received: from smtp-out-037.synserver.de ([212.40.185.37]:1066 "EHLO smtp-out-037.synserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750739AbbGBHqu (ORCPT ); Thu, 2 Jul 2015 03:46:50 -0400 X-SynServer-TrustedSrc: 1 X-SynServer-AuthUser: lars@metafoo.de X-SynServer-PPID: 29021 Message-ID: <5594EC65.9060800@metafoo.de> Date: Thu, 02 Jul 2015 09:46:45 +0200 From: Lars-Peter Clausen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-Version: 1.0 To: Kuninori Morimoto , Mark Brown CC: Linux-Kernel , Greg KH , shiiba Subject: Re: [PATCH 0/4][RFC] regmap: add force write option References: <87616ojaw9.wl%kuninori.morimoto.gx@renesas.com> In-Reply-To: <87616ojaw9.wl%kuninori.morimoto.gx@renesas.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/16/2015 10:51 AM, Kuninori Morimoto wrote: > > 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. Can you go into more detail about the exact usecase with a specific example?