From: Lee Jones <lee.jones@linaro.org>
To: "Anthony Olech <anthony.olech.opensource@diasemi.com>"
<Anthony.Olech.OpenSource@diasemi.com>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
linux-kernel@vger.kernel.org,
David Dajun Chen <david.chen@diasemi.com>
Subject: Re: [PATCH V2] mfd: da9052: Fix volatile register definition ommissions
Date: Tue, 11 Feb 2014 16:27:43 +0000 [thread overview]
Message-ID: <20140211162743.GC15081@lee--X1> (raw)
In-Reply-To: <201402111611.s1BGBXkr056672@swsrvapps-02.lan>
On Thu, 06 Feb 2014, Anthony Olech <anthony.olech.opensource@diasemi.com> wrote:
> Three of the PMIC registers have some bits that are changed
> autonomously by the PMIC itself (some time) after being set
> by some component driver of the DA9052 PMIC and hence they
> need to be marked as volatile so that the regmap API will
> not cache their values.
>
> Signed-off-by: Anthony Olech <anthony.olech.opensource@diasemi.com>
> Acked-by: David Dajun Chen <david.chen@diasemi.com>
> ---
>
> This patch is relative to linux-next repository tag next-20140206
>
> The problem was detected whilst running a scripted set of functional
> regression tests whilst investigating a different problem.
>
> This patch has been test compiled on an amd64 server for both x86
> and arm targets.
>
> This patch has been spot verified using an SMDK6410 platform
> fly-wired to a Dialog da9053 EVB.
>
> The bug that this patch fixes affects two components of DA9052 namely:
>
> WATCHDOG - the first kick will work but sebsequent ones will not
> thus the watchdog will timeout at 2 x interval.
>
> REGULATORS - the first change to any DA9052/DA9053 BUCK voltage
> will be actioned, but sebsequent ones will not.
>
> drivers/mfd/da9052-core.c | 3 +++
> 1 file changed, 3 insertions(+)
Applied, thanks.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2014-02-11 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 17:33 Anthony Olech <anthony.olech.opensource@diasemi.com>
2014-02-11 16:27 ` 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=20140211162743.GC15081@lee--X1 \
--to=lee.jones@linaro.org \
--cc=Anthony.Olech.OpenSource@diasemi.com \
--cc=david.chen@diasemi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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
Powered by JetHome