linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Bedia, Vaibhav" <vaibhav.bedia@ti.com>
Cc: "Kondratiuk, Taras" <taras@ti.com>, "Menon, Nishanth" <nm@ti.com>,
	"Mohammed, Afzal" <afzal@ti.com>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
	"rjw@sisk.pl" <rjw@sisk.pl>,
	"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
	"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
	"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Strashko, Grygorii" <grygorii.strashko@ti.com>,
	"Tseglytskyi, Andrii" <andrii.tseglytskyi@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"AnilKumar, Chimata" <anilkumar@ti.com>
Subject: Re: [RFC PATCH 0/2] cpufreq/regulator: Limit minimum voltage only
Date: Mon, 22 Apr 2013 14:25:49 +0100	[thread overview]
Message-ID: <20130422132549.GM30351@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <B5906170F1614E41A8A28DE3B8D121433EDB23C1@DBDE01.ent.ti.com>

[-- Attachment #1: Type: text/plain, Size: 676 bytes --]

On Mon, Apr 22, 2013 at 06:11:12AM +0000, Bedia, Vaibhav wrote:
> On Sat, Apr 20, 2013 at 05:54:10, Kondratiuk, Taras wrote:

> that the PMIC outputs can come is either 1.25V or 1.275V. Now i think there's
> been some confusion in the implementation phase due to things like board level
> IR drops and variations mentioned in the PMIC datasheets which has resulted in
> the tolerance being used both in am33xx.dtsi and then again in the cpufreq driver.

Note that there is support in the regulator API for putting information
in about voltage drops from the board to help compensate for things like
this.  It's just a straight linear offset but it should be OK for most
uses.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-04-22 13:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19 11:55 [RFC PATCH 0/2] cpufreq/regulator: Limit minimum voltage only Taras Kondratiuk
2013-04-19 11:55 ` [RFC PATCH 1/2] regulator: core: Add regulator_set_voltage_min() Taras Kondratiuk
2013-04-22 13:19   ` Mark Brown
2013-04-22 16:49     ` Taras Kondratiuk
2013-04-23  8:48       ` Mark Brown
2013-04-23 11:44         ` Taras Kondratiuk
2013-04-23 13:45           ` Mark Brown
2013-04-23 18:45             ` Taras Kondratiuk
2013-04-24  9:38               ` Mark Brown
2013-04-19 11:55 ` [RFC PATCH 2/2] cpufreq: cpufreq-cpu0: Limit minimum voltage only Taras Kondratiuk
2013-04-19 16:21 ` [RFC PATCH 0/2] cpufreq/regulator: " Nishanth Menon
2013-04-20  0:24   ` Kondratiuk, Taras
2013-04-22  6:11     ` Bedia, Vaibhav
2013-04-22 13:25       ` Mark Brown [this message]
2013-04-22 16:25       ` Taras Kondratiuk

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=20130422132549.GM30351@opensource.wolfsonmicro.com \
    --to=broonie@kernel.org \
    --cc=afzal@ti.com \
    --cc=andrii.tseglytskyi@ti.com \
    --cc=anilkumar@ti.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=grygorii.strashko@ti.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=rjw@sisk.pl \
    --cc=shawn.guo@linaro.org \
    --cc=taras@ti.com \
    --cc=vaibhav.bedia@ti.com \
    --cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).