public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Ramesh Gupta Guntha <grgupta77@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: PM branch updates: 3430sdp and omap3evm results
Date: Tue, 03 Feb 2009 21:42:00 -0800	[thread overview]
Message-ID: <877i46ahcn.fsf@deeprootsystems.com> (raw)
In-Reply-To: <3a2dabf50902032134tf769d73m5fe7837e6d6c79a2@mail.gmail.com> (Ramesh Gupta Guntha's message of "Wed\, 4 Feb 2009 11\:04\:35 +0530")

Ramesh Gupta Guntha <grgupta77@gmail.com> writes:

> Hi,
>
>  I am able to resolve all other issues with this pm branch except one issue,
>
> I am not able to enable the iva2 clock once system is suspended and
> resumed, I am getting below messages.
>>
>> <3>clock: dpll2_ck failed transition to 'locked'
>> clock: dpll2_ck failed transition to 'locked'
>> <3>clock: dpll2_ck failed transition to 'locked'
>> clock: dpll2_ck failed transition to 'locked'
>
> Once after booting ( without adding bridgedriver/ installing bridgedriver)
> CM_CLKEN_PLL_IVA2 value shows as 0x37 indicates IVA2 DPLL in locked mode.
>
> once after system suspend the value is not restored I am seeing that as
>  0x11 indicates IVA2 DPLL is low power stop mode.
>
> Can any one please provide your inputs on the above error? I tried
> reconfiguring the CM_CLKEN_PLL_IVA2 to lock mode but still I am seeing
> the same messages as above while enabling iva2 clock.

Are you suspending into retention or off-mode?

Kevin


  reply	other threads:[~2009-02-04  5:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 18:16 PM branch updates: 3430sdp and omap3evm results Kevin Hilman
2009-01-27 19:29 ` Koen Kooi
2009-01-27 19:52   ` Kevin Hilman
2009-01-27 20:00     ` Koen Kooi
2009-02-01 14:05 ` Ramesh Gupta Guntha
2009-02-04  5:34   ` Ramesh Gupta Guntha
2009-02-04  5:42     ` Kevin Hilman [this message]
2009-02-04  5:44       ` Ramesh Gupta Guntha
2009-02-04  6:10         ` Kevin Hilman
2009-02-04  6:24           ` Ramesh Gupta Guntha
2009-02-05 14:34             ` Kevin Hilman
2009-02-05 14:50               ` Ramesh Gupta Guntha
2009-02-10 21:01                 ` Ramesh Gupta Guntha
2009-02-10 22:28                   ` Kevin Hilman
2009-02-12  0:32                     ` Tony Lindgren
2009-02-12  1:30                       ` Ramesh Gupta Guntha
2009-02-12 12:58                         ` Ramesh Gupta Guntha
2009-02-04  6:34           ` jouni.hogander

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=877i46ahcn.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=grgupta77@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    /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