From: Nishanth Menon <nm@ti.com>
To: "Turquette, Mike" <mturquette@ti.com>
Cc: "eduardo.valentin@nokia.com" <eduardo.valentin@nokia.com>,
ext Mike Turquette <mturquette@gmail.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Sripathy, Vishwanath" <vishwanath.bs@ti.com>,
"Gopinath, Thara" <thara@ti.com>,
"Gulati, Shweta" <shweta.gulati@ti.com>,
Kevin Hilman <khilman@deeprootsystems.com>
Subject: Re: [PATCH 2/3] OMAP3630: PM: implement Foward Body-Bias for OPP1G
Date: Thu, 22 Apr 2010 08:56:53 -0500 [thread overview]
Message-ID: <4BD055A5.1050206@ti.com> (raw)
In-Reply-To: <4BCF6C6F.3030406@ti.com>
Turquette, Mike had written, on 04/21/2010 04:21 PM, the following:
[...]
>>>
>>> /**
>>> + * voltscale_adaptive_body_bias - controls ABB ldo during voltage scaling
>>> + * @target_volt: target voltage determines if ABB ldo is active or bypassed
>>> + *
>>> + * Adaptive Body-Bias is a technique in all OMAP silicon that uses the 45nm
>>> + * process. ABB can boost voltage in high OPPs for silicon with weak
>>> + * characteristics (forward Body-Bias) as well as lower voltage in low OPPs
>>> + * for silicon with strong characteristics (Reverse Body-Bias).
>>> + *
>>> + * Only Foward Body-Bias for operating at high OPPs is implemented below, per
>>> + * recommendations from silicon team.
>>> + * Reverse Body-Bias for saving power in active cases and sleep cases is not
>>> + * yet implemented.
>>> + * OMAP4 hardward also supports ABB ldo, but no recommendations have been made
>>> + * to implement it yet.
>>> + */
>>> +int voltscale_adaptive_body_bias(unsigned long target_volt)
>>> +{
>>> + u32 sr2en_enabled;
>>> + int timeout;
>>> + int sr2_wtcnt_value;
>>> +
>>> + /* calculate SR2_WTCNT_VALUE settling time */
>>> + sr2_wtcnt_value = (ABB_MAX_SETTLING_TIME *
>>> + (clk_get_rate("sys_ck") / 1000000) / 8);
>>> +
>>> + /* has SR2EN been enabled previously? */
>>> + sr2en_enabled = (prm_read_mod_reg(OMAP3430_GR_MOD,
>>> + OMAP3_PRM_LDO_ABB_CTRL_OFFSET) &
>>> + OMAP3630_SR2EN);
>>> +
>>> + /* select fast, nominal or slow OPP for ABB ldo */
>>> + /* FIXME: include OMAP4 once recommendations are complete */
>>> + if (cpu_is_omap3630() && (target_volt >= 1350000)) {
>> You are creating two steps to decide if you apply or not FBB.
>> Here and also bellow (omap voltage scale). Would it make sense to bind it
>> per opp? I mean just a flag on opp dat then you apply or not based on that flag.
>> Same for RBB.
>
> Eduardo,
>
> Thanks for reviewing.
>
> There has been some offline discussion about the best way to handle the
> the relationship between FBB enable flags and OPPs:
>
> 1) extend OPP table
> 2) piggyback on Thara's SR hwmod structures
> This probably won't work given Paul's review comments
> 3) other wacky stuff
>
> After some discussion about the best way to do this I will definitely
> lose the duplicate checks and replace with some nice table look-up.
>
> Extending the OPP table is gross for OMAP2 and OMAP3430. Piggybacking
> on SR stuff is just a hack and there is no real relationship between ABB
> ldo and SR. The crux of the issue is how to relate FBB enable flags to
> OPP table. hwmod? Ideas on this are very welcome.
>
might be a good idea for using
I vote for 2) omap_volt_data in voltage.c and using the flag there.
1) is a bad idea as ABB is not present in older silicon and opp table
should ideally be independent of silicon and contain only common data..
[...]
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2010-04-22 13:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 21:33 [PATCH 0/4] OMAP: PM: introduce Adaptive Body-Bias LDO Mike Turquette
2010-04-16 21:33 ` [PATCH 1/3] OMAP: PM: update PRM registers for ABB Mike Turquette
2010-04-19 21:23 ` Paul Walmsley
2010-04-16 21:33 ` [PATCH 2/3] OMAP3630: PM: implement Foward Body-Bias for OPP1G Mike Turquette
2010-04-19 7:46 ` Eduardo Valentin
2010-04-21 21:21 ` Mike Turquette
2010-04-22 13:56 ` Nishanth Menon [this message]
2010-04-23 7:03 ` Eduardo Valentin
2010-04-20 5:42 ` Paul Walmsley
2010-04-21 22:13 ` Mike Turquette
2010-05-21 12:44 ` Eduardo Valentin
2010-05-21 12:47 ` Eduardo Valentin
2010-05-21 15:02 ` Mike Turquette
2010-05-21 16:30 ` Eduardo Valentin
2010-04-16 21:33 ` [PATCH 3/3] HACK: OMAP3630: PM: allow testing of DVFS & FBB Mike Turquette
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=4BD055A5.1050206@ti.com \
--to=nm@ti.com \
--cc=eduardo.valentin@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@gmail.com \
--cc=mturquette@ti.com \
--cc=shweta.gulati@ti.com \
--cc=thara@ti.com \
--cc=vishwanath.bs@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 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.