From: Laxman Dewangan <ldewangan@nvidia.com>
To: Axel Lin <axel.lin@ingics.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Graeme Gregory <gg@slimlogic.co.uk>,
Liam Girdwood <lgirdwood@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFT] regulator: palmas: Remove wrong voltage setting for enabling LDO8 tracking mode
Date: Fri, 19 Apr 2013 10:19:21 +0530 [thread overview]
Message-ID: <5170CCD1.6000600@nvidia.com> (raw)
In-Reply-To: <1366341289.18636.2.camel@phoenix>
On Friday 19 April 2013 08:44 AM, Axel Lin wrote:
> When SMPS45 is set to off and LDO8 tracking is enabled, LDO8 output can be set
> from 0.45 to 1.65V and the steps of voltage change is 25mV.
>
> This is done by setting:
> pmic->desc[id].min_uV = 450000;
> pmic->desc[id].uV_step = 25000;
>
> I don't see the point of reading vsel register, multiple the register value by
> 2 and then write back to the register.
>
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> ---
> Hi Laxman,
>
> Current code looks strange (and wrong) to me.
> I don't see the point of reading vsel register, multiple the register value by
> 2 and then write back to the register.
> Can you double check this patch, in case I might misunderstand the code.
When we configure for tracking mode, the equation of voltage out put change:
Vnt = 0.9 + reg*0.05
to
Vt = 0.45 + reg*0.025
So we need to adjust the current register setting to have the same
voltage output when smps45 is OFF.
But however, just doubling the register content is not suffice here. I
did math again and it should be
reg = reg << 2 + 18.
+18 because we need to adjust the Vmin also (18 * 0.25 = 0.45).
So here we need to fix this.
prev parent reply other threads:[~2013-04-19 4:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 3:14 [PATCH RFT] regulator: palmas: Remove wrong voltage setting for enabling LDO8 tracking mode Axel Lin
2013-04-19 4:49 ` Laxman Dewangan [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=5170CCD1.6000600@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=axel.lin@ingics.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gg@slimlogic.co.uk \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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