From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: "Mike Turquette" <mturquette@linaro.org>,
"Andrii Tseglytskyi" <andrii.tseglytskyi@ti.com>,
"Tero Kristo" <t-kristo@ti.com>,
"Benoît Cousson" <b-cousson@ti.com>,
linux-omap@vger.kernel.org
Subject: Re: [RFC PATCH 5/6] ARM: OMAP3+: ABB: introduce ABB driver
Date: Tue, 2 Apr 2013 13:15:08 +0300 [thread overview]
Message-ID: <515AAFAC.50908@ti.com> (raw)
In-Reply-To: <20130402033545.GA2020@snafu>
On 04/02/2013 06:35 AM, Nishanth Menon wrote:
> On 17:05-20130401, Mike Turquette wrote:
>> OK, so we're in agreement on what The Future looks like. What does that
>> mean for Andrii's patchset?
> Unless anyone has an fundamental issue with the approach of an "Super
> regulator" controlling "sub regulators", I think, in-line with your
> view, we should probably make ABB as an regulator instead of inventing
> our own API and hooking it around clock notifiers.
Hi Nishanth, All
One question here, regarding "Super regulator" - How are you going to
differentiate
OPP changing and AVS Voltage adjustment requests to the "Super regulator"??
As you know, to select OPP changing direction, ABB type (or VC/VP
parameters)
properly you need Nominal (and only Nominal) voltage as input.
And in real world, AVS can adjust voltage, as example, for OPP100 even
low than for OPP50.
OMAP4 example:
MPU OPP Vsr Vnom ABB
OPP50 0.862249970436096 1.025 NOM
OPP100 1.03509700298309 1.2 NOM
OPPTurbo 1.09257805347443 1.325 NOM
OPPNitro 1.18703103065491 1.388 FAST
OPPNitroSB 1.29427194595337 1.398 FAST
So, while adjusting voltage, AVS can hit other OPP voltage and, as
result, ABB mode may be changed.
I think, your vision would be more clear if you could be able to provide
Sequence diagram in addition.
And would it be allowed to use DT for such regulator chain definitions
(or board-generic.c should be used instead), just for clarification,
because I have not to much DT experience:
omap443x.dtsi:
vdd_mpu: regulator-omap-ti1 { << -- Super regulator
compatible = "ti,omapX-regulator";
regulator-min-microvolt = <750000>;
regulator-max-microvolt = <1388000>;
smps-supply = <&smps_mpu>; [or smps-supply = <&vcc>;]
abb-supply = <&abb_mpu>;
};
smps_mpu: regulator-omap-smps1 { <--VC/VP regulator
compatible = "ti,omapX-smps-regulator";
ti,vc = <&vc>
ti,vp = <&vp_mpu>
};
twl4030.dtsi
vcc: regulator-vdd1 {
compatible = "ti,twl4030-vdd1";
regulator-min-microvolt = <600000>;
regulator-max-microvolt = <1450000>;
};
Regards,
Grygorii Strashko
next prev parent reply other threads:[~2013-04-02 10:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 17:16 [PATCH 1/6] ARM: dts: OMAP36xx: add device tree for ABB Andrii Tseglytskyi
2013-03-28 17:16 ` [PATCH 2/6] ARM: dts: OMAP4: " Andrii Tseglytskyi
2013-03-28 17:16 ` [PATCH 3/6] ARM: dts: OMAP5: " Andrii Tseglytskyi
2013-03-28 17:16 ` [PATCH 4/6] ARM: OMAP3+: ABB: add aliases for clocks used in ABB driver Andrii Tseglytskyi
2013-03-28 17:16 ` [PATCH 5/6] ARM: OMAP3+: ABB: introduce " Andrii Tseglytskyi
2013-03-28 21:27 ` Mike Turquette
2013-03-28 22:35 ` Nishanth Menon
2013-04-01 11:04 ` Andrii Tseglytskyi
2013-04-01 11:07 ` Andrii Tseglytskyi
[not found] ` <51596725.9060109@ti.com>
2013-04-01 18:10 ` [RFC PATCH " Mike Turquette
2013-04-01 19:28 ` Nishanth Menon
[not found] ` <20130401213430.8177.21940@quantum>
2013-04-01 23:00 ` Nishanth Menon
[not found] ` <20130402000545.8177.65252@quantum>
2013-04-02 3:35 ` Nishanth Menon
2013-04-02 10:15 ` Grygorii Strashko [this message]
2013-04-02 12:49 ` Nishanth Menon
[not found] ` <20130402171614.8177.68752@quantum>
2013-04-02 17:35 ` Andrii Tseglytskyi
2013-04-03 2:00 ` Nishanth Menon
2013-04-03 20:09 ` Mike Turquette
2013-03-28 17:16 ` [PATCH 6/6] ARM: OMAP3+: ABB: introduce debugfs entry Andrii Tseglytskyi
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=515AAFAC.50908@ti.com \
--to=grygorii.strashko@ti.com \
--cc=andrii.tseglytskyi@ti.com \
--cc=b-cousson@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=nm@ti.com \
--cc=t-kristo@ti.com \
/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).