public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Barada <peterb@logicpd.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: Russ Dill <russ.dill@gmail.com>, "Premi, Sanjeev" <premi@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: PM branch rebased to 2.6.29
Date: Mon, 30 Mar 2009 14:18:06 -0400	[thread overview]
Message-ID: <1238437086.8002.137.camel@blackhole> (raw)
In-Reply-To: <878wmm3nbx.fsf@deeprootsystems.com>

On Mon, 2009-03-30 at 10:57 -0700, Kevin Hilman wrote:
> Russ Dill <russ.dill@gmail.com> writes:
> 
> > On Mon, Mar 30, 2009 at 3:08 AM, Premi, Sanjeev <premi@ti.com> wrote:
> [...]
> 
> >> I had found that two drivers that could prevent clocks_off are
> >> USB and DSS because of the way they use clk_enable().
> >>
> >> Can you try building without theses drivers just for verification?
> >>
> >
> > Building without dss makes things worse:
> >
> > Powerdomain (dss_pwrdm) didn't enter target state 0
> >
> > Maybe by looking at what the dss driver is doing I can get core and
> > per to turn off.
> 
> Peter,
> 
> Have you tried with the debug patch I sent?  If you can test with that
> patch, and send the output, I can tell you what is preventing you from
> hitting RET.

No, not yet.  After comments by Kevin and others regarding my DPLL
setting being wrong from u-boot, I'm currently trying to bring up u-boot
from the Beagle on the LV SOM.  Then I can get the timings for the SDRC
correct, and then work on getting the lates PM rebase (2.6.29) to boot.
When I tried it with my current u-boot (based on 1.1.4 labrador), it
would sporadically hang in rtc_hctosys and other functions that tried to
talk to the twl4030 via i2c...

I'm running into problems with u-boot (cloned the Beagle config) where
I2C to setup power domains fails after the first write (bus gets stuck
busy).

> FWIW, the latest HEAD of the PM branch has that debug patch included.
> 
> After doing the suspend/resume, just
> 
> # cat /debug/pm_debug/registers/1
> 
> and attach the output.
> 
> Kevin
> 
-- 
Peter Barada <peterb@logicpd.com>

  reply	other threads:[~2009-03-30 18:18 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18  5:21 PM branch rebased to 2.6.29 Kevin Hilman
2009-03-18  7:41 ` Artem Bityutskiy
2009-03-18 15:51   ` Kevin Hilman
2009-03-19 22:20 ` David Brownell
2009-03-20 18:59   ` Tony Lindgren
2009-03-20 19:46     ` David Brownell
2009-03-20 19:57       ` Tony Lindgren
2009-03-20 21:27         ` Tony Lindgren
2009-03-20 22:36       ` David Brownell
2009-03-24 17:10 ` Peter Barada
2009-03-24 18:08   ` Kevin Hilman
2009-03-24 20:11     ` Peter Barada
2009-03-24 20:21       ` Kevin Hilman
2009-03-24 20:37         ` Peter Barada
2009-03-27 20:50         ` Russ Dill
2009-03-30 10:08           ` Premi, Sanjeev
2009-03-30 10:42             ` Koen Kooi
2009-03-30 13:22               ` Premi, Sanjeev
2009-03-30 17:44             ` Russ Dill
2009-03-30 17:57               ` Kevin Hilman
2009-03-30 18:18                 ` Peter Barada [this message]
2009-03-30 18:43               ` Kevin Hilman
2009-03-30 23:01                 ` Russ Dill
2009-03-31  7:01                   ` Russ Dill
2009-03-31 18:25                   ` Kevin Hilman
2009-03-31 21:31                     ` Russ Dill
2009-03-31 23:33                       ` Kevin Hilman
2009-04-01  1:30                         ` Russ Dill
2009-04-01  4:11                           ` Kevin Hilman
2009-03-26 16:54 ` Jean Pihet
2009-03-26 17:01   ` Kevin Hilman

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=1238437086.8002.137.camel@blackhole \
    --to=peterb@logicpd.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=premi@ti.com \
    --cc=russ.dill@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox