From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kevin Hilman <khilman@deeprootsystems.com>
Subject: Re: [PATCH 1/2] OMAP3 PM: move omap3 sleep to ddr
Date: Mon, 22 Nov 2010 10:23:37 -0800
Message-ID: <87tyj9tdxy.fsf@deeprootsystems.com>
References: <87tyjey6h3.fsf@deeprootsystems.com> <4CE55A88.6010300@ti.com>
	<20101118175215.GE9264@atomide.com>
	<AANLkTi=bhULQsXhnN9ugDm7k=2P4E7-SvXEnx06pBwmu@mail.gmail.com>
	<20101118182752.GI9264@atomide.com>
	<AANLkTi=m1MXATmUzXNxbggoUS01AbyeGZm9WMgWUqdNo@mail.gmail.com>
	<AANLkTikztB6aSir83P4odPznmvXGvq0uzYhRN2UWC1Dr@mail.gmail.com>
	<92CDD168D1E81F4F9D3839DC45903FC6A5E5A085@dlee03.ent.ti.com>
	<20101122100716.GC26003@nokia.com>
	<87bp5hz6og.fsf@deeprootsystems.com>
	<20101122162224.GH26003@nokia.com> <4CEA998A.7060406@ti.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <linux-omap-owner@vger.kernel.org>
Received: from mail-pz0-f46.google.com ([209.85.210.46]:58999 "EHLO
	mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750790Ab0KVSXk (ORCPT
	<rfc822;linux-omap@vger.kernel.org>); Mon, 22 Nov 2010 13:23:40 -0500
Received: by pzk6 with SMTP id 6so184576pzk.19
        for <linux-omap@vger.kernel.org>; Mon, 22 Nov 2010 10:23:40 -0800 (PST)
In-Reply-To: <4CEA998A.7060406@ti.com> (Nishanth Menon's message of "Mon, 22
	Nov 2010 10:25:46 -0600")
Sender: linux-omap-owner@vger.kernel.org
List-Id: linux-omap@vger.kernel.org
To: Nishanth Menon <nm@ti.com>
Cc: Peter 'p2' De Schrijver <peter.de-schrijver@nokia.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>

Nishanth Menon <nm@ti.com> writes:

> 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.

It would be worth noting other known issues that are not worked around
in this series due to external dependencies.

Also, is the current SR/voltage series as proposed capable of handling
the workaround for this fix?

Kevin