linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: "Opensource [Steve Twiss]" <stwiss.opensource@diasemi.com>
Cc: LINUXKERNEL <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V1] mfd: da9062: fix missing volatile registers in the core regmap_range volatile lists
Date: Thu, 11 Feb 2016 09:17:31 +0000	[thread overview]
Message-ID: <20160211091731.GD3782@x1> (raw)
In-Reply-To: <6ED8E3B22081A4459DAC7699F3695FB70173D30C81@SW-EX-MBX02.diasemi.com>

On Wed, 10 Feb 2016, Opensource [Steve Twiss] wrote:

> 
> On 10 February 2016 16:56, Lee Jones wrote:
> 
> > To: Opensource [Steve Twiss]
> > Cc: LINUXKERNEL; David Dajun Chen; Support Opensource
> > Subject: Re: [PATCH V1] mfd: da9062: fix missing volatile registers in the core
> > regmap_range volatile lists
> > 
> > On Mon, 01 Feb 2016, Steve Twiss wrote:
> > 
> > > From: Steve Twiss <stwiss.opensource@diasemi.com>
> > >
> > > Add an updated set of registers listed in the core regmap_range volatile
> > > ranges defined for the DA9062.
> > >
> > > These new registers contain bits that cannot be considered under the full
> > > control of software. Under various conditions the hardware will set and/or
> > > automatically clear bit(s) contained in these registers.
> > >
> > > When using a cached version of regmap, the volatility of these registers must
> > > be identified otherwise the regmap operations may not ensure the registers
> > > are explicitly altered.
> > >
> > > As well as updating the list of volatile registers, this change will fix a
> > > corner case discovered in the DA9063 ONKEY which is used by the DA9062 core.
> > >
> > > In the ONKEY case, the CONTROL_B register is now listed as volatile in the
> > > regmap_range because it contains the bit field NONKEY_LOCK. This bit can be
> > > altered by hardware, in which case regmap must be notified of its ability
> > > to be manpiulated outside of software control.
> > >
> > > Signed-off-by: Steve Twiss <stwiss.opensource@diasemi.com>
> > 
> > Applied, thanks.
> 
> Thanks.
> Regards,
> Steve

No need for thank yous.  They're implied. ;)

[... and they just account for churn in my already very busy inbox].

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      reply	other threads:[~2016-02-11  9:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01 16:09 [PATCH V1] mfd: da9062: fix missing volatile registers in the core regmap_range volatile lists Steve Twiss
2016-02-10 16:56 ` Lee Jones
2016-02-10 17:01   ` Opensource [Steve Twiss]
2016-02-11  9:17     ` Lee Jones [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160211091731.GD3782@x1 \
    --to=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stwiss.opensource@diasemi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).