> > > 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.
> > >
> -Original Message-
> From: Lee Jones [mailto:lee.jo...@linaro.org]
> Sent: 03 February 2014 10:29
> To: Opensource [Anthony Olech]
> Cc: Mark Brown; Samuel Ortiz; linux-kernel@vger.kernel.org; David Dajun
> Chen
> Subject: Re: [PATCH V1] fix da9052 volatile register
> 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
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
-Original Message-
From: Lee Jones [mailto:lee.jo...@linaro.org]
Sent: 03 February 2014 10:29
To: Opensource [Anthony Olech]
Cc: Mark Brown; Samuel Ortiz; linux-kernel@vger.kernel.org; David Dajun
Chen
Subject: Re: [PATCH V1] fix da9052 volatile register definition ommissions
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
6 matches
Mail list logo