From: Nishanth Menon <nm@ti.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: "Gopinath, Thara" <thara@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Gulati, Shweta" <shweta.gulati@ti.com>
Subject: Re: [PATCH] OMAP3: PM: Fix for Silicon bug on Context Restore on OMAP3430
Date: Tue, 6 Oct 2009 10:17:44 -0500 [thread overview]
Message-ID: <4ACB5F98.2080603@ti.com> (raw)
In-Reply-To: <87eipgr29j.fsf@deeprootsystems.com>
Kevin Hilman had written, on 10/06/2009 10:05 AM, the following:
> "Gopinath, Thara" <thara@ti.com> writes:
>
>> Will repost the patch with the defconfig option added. So that this can be disabled if not needed.
>
> ok, please update the changelog as well as describe the 300usec value
> in terms of cycles. IOW, is 300usecs going to work at lower OPPs also?
>
Could I request for 2 options:
a) workaround with no delay (manual save restore) - power savings for
boards which dont use the pin
b) workaround with 300uSec - for boards which use the pin ->functional
Also please have a check based on CPU revision and add errata number?
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2009-10-06 15:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1254741761-31546-1-git-send-email-y>
2009-10-05 11:51 ` [PATCH] OMAP3: PM: Fix for Silicon bug on Context Restore on OMAP3430 Shilimkar, Santosh
2009-10-05 17:04 ` Kevin Hilman
2009-10-05 17:27 ` Nishanth Menon
2009-10-06 6:59 ` Gopinath, Thara
2009-10-06 11:50 ` Nishanth Menon
2009-10-06 13:17 ` Kevin Hilman
2009-10-06 13:31 ` Gopinath, Thara
2009-10-06 14:20 ` Kevin Hilman
2009-10-06 14:35 ` Gopinath, Thara
2009-10-06 14:49 ` Kevin Hilman
2009-10-06 14:54 ` Gopinath, Thara
2009-10-06 15:05 ` Kevin Hilman
2009-10-06 15:17 ` Nishanth Menon [this message]
2009-10-06 15:23 ` Gopinath, Thara
2009-10-06 15:25 ` Nishanth Menon
2009-10-05 11:22 y
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=4ACB5F98.2080603@ti.com \
--to=nm@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=shweta.gulati@ti.com \
--cc=thara@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.