From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755619AbbCFMpl (ORCPT ); Fri, 6 Mar 2015 07:45:41 -0500 Received: from smtp-out-063.synserver.de ([212.40.185.63]:1087 "EHLO smtp-out-061.synserver.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752009AbbCFMpj (ORCPT ); Fri, 6 Mar 2015 07:45:39 -0500 X-SynServer-TrustedSrc: 1 X-SynServer-AuthUser: lars@metafoo.de X-SynServer-PPID: 6222 Message-ID: <54F9A171.5000107@metafoo.de> Date: Fri, 06 Mar 2015 13:45:37 +0100 From: Lars-Peter Clausen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.5.0 MIME-Version: 1.0 To: Mark Brown , Daniel Baluta CC: Linux Kernel Mailing List Subject: Re: Using regmap_update_bits to update a write only register References: <20150305175356.GB21293@sirena.org.uk> <20150306112142.GG21293@sirena.org.uk> In-Reply-To: <20150306112142.GG21293@sirena.org.uk> 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 03/06/2015 12:21 PM, Mark Brown wrote: > On Thu, Mar 05, 2015 at 08:14:14PM +0200, Daniel Baluta wrote: >> On Mar 5, 2015 7:54 PM, "Mark Brown" wrote: > >>> Probably, or there's a bug. What should happen is that if the register >>> default appeared successfully then the read will get statisfied from the >>> cache in the manner you describe - presumably that's gone wrong somehow. >>> Have you set num_reg_defaults? That's the obvious thing... > >> Did that. I will have a closer look. Thanks for the answer. > > OK, the other thing that springs to mind to check is that the register > didn't somehow get marked as volatile. > There were some bugs in the past were non-readable register automatically got marked as volatile, this has been fixed though a few months ago. Try to make sure you use the latest upstream version of regmap. - Lars