From: Laxman Dewangan <ldewangan@nvidia.com>
To: Axel Lin <axel.lin@ingics.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lgirdwood@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: regulator: tps80031: question about LDO2 TRACK_MODE_ENABLE of TPS80031 or TPS80032-ES1.0
Date: Wed, 17 Apr 2013 12:14:29 +0530 [thread overview]
Message-ID: <516E44CD.3010203@nvidia.com> (raw)
In-Reply-To: <1366169084.10398.4.camel@phoenix>
On Wednesday 17 April 2013 08:54 AM, Axel Lin wrote:
> hi Laxman,
>
> Currently we have below code in tps80031_ldo_set_voltage_sel():
>
> /* Check for valid setting for TPS80031 or TPS80032-ES1.0 */
> if ((ri->rinfo->desc.id == TPS80031_REGULATOR_LDO2) &&
> (ri->device_flags & TRACK_MODE_ENABLE)) {
> unsigned nvsel = (sel) & 0x1F;
> if (((tps80031_get_chip_info(parent) == TPS80031) ||
> ((tps80031_get_chip_info(parent) == TPS80032) &&
> (tps80031_get_pmu_version(parent) == 0x0))) &&
> ((nvsel == 0x0) || (nvsel >= 0x19 && nvsel <= 0x1F))) {
> dev_err(ri->dev,
> "Invalid sel %d in track mode LDO2\n",
> nvsel);
> return -EINVAL;
> }
> }
>
> However, list_voltage() still show these invalid selectors have supported voltage.
> Besides, having the code "nvsel = (sel) & 0x1F" looks a bit odd, because currently
> n_voltages is set to 57 when TRACK_MODE_ENABLE is set.
>
> I'm wondering if below comment is still true for LDO2 TRACK_MODE_ENABLE of
> "TPS80031/TPS80032-ES1.0"?
>
> /* TRACK mode the ldo2 varies from 600mV to 1300mV */
>
> What is the register value && voltage mapping for LDO2 TRACK_MODE_ENABLE of
> TPS80031 or TPS80032-ES1.0?
Hi Axel,
Following the excerpt of the mail got from TI on this issue:
There is a bug on LDO2 tracking on TPS80031 and TPS80032 ES1.0 but you
should be able to have the functionality working.
Issue description:
- LDO2 traking mode is enabled
- LDO2 tracks SMPS2 voltage.
- LDO2 automatically switch-off when LDO2_CFG_VOLTAGE is changed to some
discrete values (non exhaustive list):
00011001, 00011010, 00011011, 00011100, .
- LDO2 switch-on again when LDO2_CFG_VOLTAGE is changed to other values
(non exhaustive list):
00011000, 00010111, .
LDOs have reserved codes. For these codes, LDO is switch-off.
In tracking, LDO2 ref comes from SMPS2.
However LDO2 enable is still gated by LDO2 VSEL decoding.
As a result, in tracking mode LDO2 will be disabled for following code
(SMPS VSEL format):
000000 & 100000 (MSB not decoded)
011001 & 111001 (MSB not decoded)
011010 & 111010 (MSB not decoded)
011100 & 111100 (MSB not decoded)
011101 & 111101 (MSB not decoded)
011110 & 111110 (MSB not decoded)
Therefore, we made this voltage to be invalid on above case.
prev parent reply other threads:[~2013-04-17 6:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 3:24 regulator: tps80031: question about LDO2 TRACK_MODE_ENABLE of TPS80031 or TPS80032-ES1.0 Axel Lin
2013-04-17 6:44 ` 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=516E44CD.3010203@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=axel.lin@ingics.com \
--cc=broonie@opensource.wolfsonmicro.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.