From: Lee Jones <lee.jones@linaro.org>
To: "Anthony Olech <anthony.olech.opensource@diasemi.com>"
<Anthony.Olech.OpenSource@diasemi.com>
Cc: Mark Brown <broonie@kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
linux-kernel@vger.kernel.org,
David Dajun Chen <david.chen@diasemi.com>
Subject: Re: [PATCH V1] fix da9052 volatile register definition ommissions
Date: Mon, 3 Feb 2014 10:29:19 +0000 [thread overview]
Message-ID: <20140203102919.GP13529@lee--X1> (raw)
In-Reply-To: <201401281723.s0SHNmLa041140@swsrvapps-02.lan>
> 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>
> Signed-off-by: David Dajun Chen <david.chen@diasemi.com>
These are not correct.
Who authored the patch?
> ---
> This patch is relative to linux-next repository tag next-20140128
>
> 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 will timeout at 2 x interval.
>
> REGULATORS - the first change to any DA9052 BUCK voltage will be
> actioned, but sebsequent ones will not.
Which patch caused the bug?
> drivers/mfd/da9052-core.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/mfd/da9052-core.c b/drivers/mfd/da9052-core.c
> index 25838f1..e8af816 100644
> --- a/drivers/mfd/da9052-core.c
> +++ b/drivers/mfd/da9052-core.c
> @@ -279,6 +279,9 @@ static bool da9052_reg_volatile(struct device *dev, unsigned int reg)
> case DA9052_EVENT_B_REG:
> case DA9052_EVENT_C_REG:
> case DA9052_EVENT_D_REG:
> + case DA9052_CONTROL_B_REG:
> + case DA9052_CONTROL_D_REG:
> + case DA9052_SUPPLY_REG:
> case DA9052_FAULTLOG_REG:
> case DA9052_CHG_TIME_REG:
> case DA9052_ADC_RES_L_REG:
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-02-03 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 16:45 [PATCH V1] fix da9052 volatile register definition ommissions Anthony Olech <anthony.olech.opensource@diasemi.com>
2014-02-03 10:29 ` Lee Jones [this message]
2014-02-03 16:11 ` Opensource [Anthony Olech]
2014-02-03 16:47 ` Lee Jones
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=20140203102919.GP13529@lee--X1 \
--to=lee.jones@linaro.org \
--cc=Anthony.Olech.OpenSource@diasemi.com \
--cc=broonie@kernel.org \
--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