From: Kevin Hilman <khilman@deeprootsystems.com>
To: Lesly Arackal Manuel <leslyam@ti.com>
Cc: linux-omap@vger.kernel.org, 'Nishanth Menon' <nm@ti.com>,
'David Derrick' <dderrick@ti.com>,
'Samuel Ortiz' <sameo@linux.intel.com>
Subject: Re: [PATCH v3 2/5] omap3: pm: Using separate clk/volt setup_time for RET and OFF states
Date: Fri, 19 Mar 2010 10:34:53 -0700 [thread overview]
Message-ID: <87ocikxlj6.fsf@deeprootsystems.com> (raw)
In-Reply-To: <009c01cac732$5d237ee0$518918ac@apr.dhcp.ti.com> (Lesly Arackal Manuel's message of "Fri\, 19 Mar 2010 12\:34\:04 +0530")
Please don't top post: http://www.elinux.org/Netiquette
"Lesly Arackal Manuel" <leslyam@ti.com> writes:
> Hi Kevin,
>
> If my understanding is correct.
>
> The clk_setuptime is board specific, depends on the osc/XTAL used on the
> board. So the clk_setuptime has to come from the board file.
>
> Volt_setuptime & volt_offset is PM IC specific, depends on the PM IC's SMPS
> characteristics. So this can be updated from the script file.
>
> Finally the voltage cmd values (on, onlp, ret &off) is Si Specific, Varies
> with Si(OMAP3430, OMAP3630, ...). So can be updated in voltage file itself.
Then, all the defaults should be in SoC specific code with the ability
for board files to override clk_setuptime.
Kevin
>
> Just correct if I'm wrong.
>
> Thanks & Regards,
> Lesly A M
>
> -----Original Message-----
> From: Kevin Hilman [mailto:khilman@deeprootsystems.com]
> Sent: Friday, March 19, 2010 5:00 AM
> To: Lesly A M
> Cc: linux-omap@vger.kernel.org; Lesly A M; Nishanth Menon; David Derrick;
> Samuel Ortiz
> Subject: Re: [PATCH v3 2/5] omap3: pm: Using separate clk/volt setup_time
> for RET and OFF states
>
> Lesly A M <leslyam@ti.com> writes:
>
>> Copied the setuptime in each board file, since OMAP3430 & OMAP3630
>> has different voltage levels for the same states.
>
> So that suggests there should be 2 tables (one per SoC), rather than
> one for each board file. IOW, the setup times are SoC specific, not
> board specific, so they don't belong in board files.
>
> Kevin
prev parent reply other threads:[~2010-03-19 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 15:31 [PATCH v3 2/5] omap3: pm: Using separate clk/volt setup_time for RET and OFF states Lesly A M
2010-03-18 23:29 ` Kevin Hilman
2010-03-19 7:04 ` Lesly Arackal Manuel
2010-03-19 17:34 ` Kevin Hilman [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=87ocikxlj6.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=dderrick@ti.com \
--cc=leslyam@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=sameo@linux.intel.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