public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Elvis Dowson <elvis.dowson@mac.com>
Cc: Linux OMAP Users <linux-omap@vger.kernel.org>
Subject: Re: PM error: Powerdomain (core_pwddm) didn't enter target state 1
Date: Fri, 05 Jun 2009 10:49:41 -0700	[thread overview]
Message-ID: <87tz2ua7uy.fsf@deeprootsystems.com> (raw)
In-Reply-To: <277E4F10-4228-40C5-85C8-5B365B861DFF@mac.com> (Elvis Dowson's message of "Fri\, 05 Jun 2009 21\:34\:29 +0400")

Elvis Dowson <elvis.dowson@mac.com> writes:

> Hi Kevin,
>
> On Jun 5, 2009, at 7:53 PM, Kevin Hilman wrote:
>
>>>
>>
>> It's pretty difficult for me to know what you are actually running by
>> the description above.  You've taken a bunch of stuff, put them
>> together in some unspecified way, and are using an unspecified config.
>
> Sorry about that, I'm working on an android port to the gumstix overo
> earth platform. I'm trying to incorporate patches from the
> android-2.6.29 kernel, tomi's latest dss2 patches and your pm patches,
> to the linux-omap-2.6 master branch.

For initial PM debugging, I highly recommend something closer to what
others are developing and testing against.  Using the PM branch
patches on top of linux-omap master is not yet tested and validated,
so I can't give you any support there.

For example, you might start from the Android OMAP kernel which
is 2.6.29 based and includes the PM branch already.

  http://android.git.kernel.org/?p=kernel/omap.git

Then you'd just have to add your dss2 and Overo stuff there.

Kevin

  parent reply	other threads:[~2009-06-05 17:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <42B46BA8-AF35-42B5-9616-EADA31EF0553@mac.com>
2009-06-05 15:42 ` PM error: Powerdomain (core_pwddm) didn't enter target state 1 Wang Sawsd-A24013
2009-06-05 15:53 ` Kevin Hilman
     [not found]   ` <277E4F10-4228-40C5-85C8-5B365B861DFF@mac.com>
2009-06-05 17:49     ` Kevin Hilman [this message]
2009-06-06  0:44       ` Rebecca Schultz Zavin
2009-06-06  7:38         ` Koen Kooi

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=87tz2ua7uy.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=elvis.dowson@mac.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