From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: Laxman Dewangan <ldewangan.com@nvidia.com>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH V1] TPS62360: Add tps62360 regulator driver
Date: Fri, 6 Jan 2012 09:44:39 -0800 [thread overview]
Message-ID: <20120106174438.GA3485@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <96C9D994977DD0439FB6D3FE3B13DD907DBD3A9E9B@BGMAIL01.nvidia.com>
On Thu, Jan 05, 2012 at 07:18:25PM +0530, Laxman Dewangan wrote:
Please fix your mailer to word wrap at less than 80 columns. I've
reflowed your text for legibility.
> > > + /* Configure the output discharge path */
> > > + st = tps62360_reg_modify_bits(tps, REG_RAMPCTRL, BIT(2), BIT(2));
> > > + if (st < 0)
> > > + dev_err(tps->dev, "%s() fails in updating reg %d\n",
> > > + __func__, REG_RAMPCTRL);
> > > +}
> > I rather suspect that if this is worth doing it's also worth doing over
> > suspend...
> The discharge path should be only enabled when the output voltage will go to 0.
> If it stay in non-zero voltage and enabling discharge path will consume more power.
> In suspend, it is not necessarily that voltage output will be 0 and hence it should not
> be enabled. In shutdown all power goes off from pmu and hence it is worth to enable
> discharge path for quick fall of output voltage.
> >
> > > + * @vsel: Select the voltage id register.
> >
> > What's this?
> There is 4 sets of voltage configuration register for voltage output. The power
> on reset values for this registers are different and selection of the voltage
> configuration register is done by 2 pins of the pmu chip which is board dependent.
> Based on board connection, it need to be program the desired voltage configuration
> Register to achieve the desired output.
>
next prev parent reply other threads:[~2012-01-06 17:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 9:20 [PATCH V1] TPS62360: Add tps62360 regulator driver Laxman Dewangan
2012-01-05 6:29 ` Mark Brown
2012-01-05 13:48 ` Laxman Dewangan
2012-01-06 17:44 ` Mark Brown [this message]
2012-01-06 18:57 ` Mark Brown
2012-01-07 17:46 ` Laxman Dewangan
2012-01-07 19:10 ` Mark Brown
2012-01-08 7:42 ` Laxman Dewangan
2012-01-08 16:58 ` Mark Brown
2012-01-09 7:04 ` Laxman Dewangan
2012-01-09 7:11 ` Mark Brown
2012-01-09 7:33 ` Laxman Dewangan
2012-01-09 7:39 ` Mark Brown
2012-01-09 8:47 ` Laxman Dewangan
2012-01-09 8:48 ` Mark Brown
2012-01-09 9:19 ` Laxman Dewangan
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=20120106174438.GA3485@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=ldewangan.com@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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