From: Nishanth Menon <nm@ti.com>
To: Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com>
Cc: ext Kevin Hilman <khilman@deeprootsystems.com>,
"ext Derrick, David" <dderrick@ti.com>,
Jean Pihet <jean.pihet@newoldbits.com>,
Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Sripathy, Vishwanath" <vishwanath.bs@ti.com>,
"Pihet-XID, Jean" <j-pihet@ti.com>
Subject: Re: [PATCH 1/2] OMAP3 PM: move omap3 sleep to ddr
Date: Mon, 22 Nov 2010 10:25:46 -0600 [thread overview]
Message-ID: <4CEA998A.7060406@ti.com> (raw)
In-Reply-To: <20101122162224.GH26003@nokia.com>
Peter 'p2' De Schrijver had written, on 11/22/2010 10:22 AM, the following:
[...]
>>> The root cause for the DLL not locking has been found though and a
>>> workaround implemented. So it should work now :)
>> Is the workaround for this reflected in Nishanth's series?
>
> No. It seems not. The workaround needs VDD2 voltage scaling which seems
> to be missing now from l-o ?
yep, that is correct - we dont have dvfs/OPP/voltage scaling in
kernel.org as of today - until we have those, it might not be possible
to push the "real workaround". the mentioned patch is, as documented,
support for the voltage workaround.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2010-11-22 16:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 14:51 OMAP3 sleep code clean-up Jean Pihet
2010-11-18 14:51 ` [PATCH 1/2] OMAP3 PM: move omap3 sleep to ddr Jean Pihet
2010-11-18 14:57 ` Nishanth Menon
2010-11-18 15:08 ` Sripathy, Vishwanath
2010-11-18 15:11 ` Nishanth Menon
2010-11-18 15:15 ` Jean Pihet
2010-11-18 15:33 ` Nishanth Menon
2010-11-18 15:52 ` Kevin Hilman
2010-11-18 16:55 ` Nishanth Menon
2010-11-18 17:52 ` Tony Lindgren
2010-11-18 18:13 ` Tony Lindgren
2010-11-18 18:15 ` Jean Pihet
2010-11-18 18:27 ` Tony Lindgren
2010-11-18 18:34 ` Jean Pihet
2010-11-19 15:37 ` Jean Pihet
2010-11-19 16:09 ` Tony Lindgren
2010-11-19 16:14 ` Derrick, David
2010-11-19 16:26 ` Jean Pihet
2010-11-22 10:07 ` Peter 'p2' De Schrijver
2010-11-22 16:03 ` Kevin Hilman
2010-11-22 16:08 ` Jean Pihet
2010-11-22 16:22 ` Peter 'p2' De Schrijver
2010-11-22 16:25 ` Nishanth Menon [this message]
2010-11-22 18:23 ` Kevin Hilman
2010-11-22 18:31 ` Nishanth Menon
2010-11-18 14:51 ` [PATCH 2/2] OMAP3: clean up ASM idle code Jean Pihet
2010-11-18 17:41 ` Tony Lindgren
2010-11-18 18:19 ` Jean Pihet
-- strict thread matches above, loose matches on Subject: below --
2010-09-24 10:56 [PATCH 0/2] OMAP3 PM: sleep code clean up Vishwanath BS
2010-09-24 10:56 ` [PATCH 1/2] OMAP3 PM: move omap3 sleep to ddr Vishwanath BS
2010-09-24 19:01 ` Tony Lindgren
2010-09-24 19:09 ` Tony Lindgren
[not found] ` <20100924190930.GH4211-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2010-09-25 5:52 ` Shilimkar, Santosh
2010-09-24 19:57 ` Kevin Hilman
2010-10-04 7:26 ` Sripathy, Vishwanath
2010-09-24 10:47 [PATCH 0/2] OMAP3 PM: sleep code clean up Vishwanath BS
2010-09-24 10:47 ` [PATCH 1/2] OMAP3 PM: move omap3 sleep to ddr Vishwanath BS
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=4CEA998A.7060406@ti.com \
--to=nm@ti.com \
--cc=dderrick@ti.com \
--cc=j-pihet@ti.com \
--cc=jean.pihet@newoldbits.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.de-schrijver@nokia.com \
--cc=tony@atomide.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.