From: Nishanth Menon <nm@ti.com>
To: "Dasgupta, Romit" <romit@ti.com>
Cc: "Reddy, Teerth" <teerth@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] OMAP3: PM: Dynamic calculation of SDRC clock stabilization delay
Date: Fri, 11 Dec 2009 07:42:51 -0600 [thread overview]
Message-ID: <4B224C5B.3080808@ti.com> (raw)
In-Reply-To: <4B223BA3.4000402@ti.com>
Dasgupta, Romit had written, on 12/11/2009 06:31 AM, the following:
>> Also Richard indicated that there might be a few tricky things with perf
>> Counters with specific devices - like EMU/HS/GP devices. It might need EMU
>> Domain for the values to pass through and there might be a yet-not-measured increase In power which could impact usage numbers and may need additional
>> Code to switch off the domain correctly while hitting OFF/RET..
>>
>
> Yes someone with EMU/HS could run and let us know. OTOH there won't be any
> increase in power as it is done only once during boot time after which the
> perfcounters are stopped.
>
> By the way can you run this in 3630 and help us find what is the SRAM access
> delay? I am sure it should be lesser since it has a process improvement over 34xx.
>
>
will try on SDP3630 among the boards that I have around. meanwhile,
would like an explanation to my previous comments also esp on the black
magic "6" ;) - thanks.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2009-12-11 13:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 12:05 [PATCH] OMAP3: PM: Dynamic calculation of SDRC clock stabilization delay Reddy, Teerth
2009-12-11 12:23 ` Menon, Nishanth
2009-12-11 12:31 ` Romit Dasgupta
2009-12-11 13:42 ` Nishanth Menon [this message]
2009-12-12 4:43 ` Nishanth Menon
2009-12-14 8:19 ` Romit Dasgupta
2009-12-11 13:14 ` Jean Pihet
2009-12-11 14:07 ` Romit Dasgupta
2009-12-11 16:38 ` Kevin Hilman
2009-12-12 0:49 ` Kevin Hilman
2009-12-14 9:01 ` Romit Dasgupta
2009-12-14 16:10 ` Kevin Hilman
2009-12-14 16:41 ` Dasgupta, Romit
2009-12-14 19:34 ` Kevin Hilman
2009-12-21 11:44 ` Reddy, Teerth
2009-12-22 15:56 ` Kevin Hilman
2009-12-22 16:00 ` Sripathy, Vishwanath
2009-12-22 16:56 ` Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2009-12-24 5:33 Reddy, Teerth
2009-12-24 10:31 ` Romit Dasgupta
2009-12-28 19:57 ` Tony Lindgren
2010-01-06 23:06 ` Kevin Hilman
2010-01-21 5:35 ` Paul Walmsley
2010-01-21 8:58 ` Reddy, Teerth
2010-02-08 22:52 ` Paul Walmsley
2009-12-23 13:56 Reddy, Teerth
2009-12-23 14:32 ` Romit Dasgupta
2009-12-24 5:31 ` Reddy, Teerth
2009-12-11 12:42 Romit Dasgupta
2009-12-11 10:35 Reddy, Teerth
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=4B224C5B.3080808@ti.com \
--to=nm@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=romit@ti.com \
--cc=teerth@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