linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grazvydas Ignotas <notasas@gmail.com>
To: Kevin Hilman <khilman@ti.com>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	Paul Walmsley <paul@pwsan.com>
Subject: Re: DSS pwrdm usecount, disabling autodeps for DSS
Date: Fri, 9 Mar 2012 13:08:17 +0200	[thread overview]
Message-ID: <CANOLnOOdnJ4OGrhBdF5h_NyYHZ4FPsJet+0M=fGCygQDOsWByQ@mail.gmail.com> (raw)
In-Reply-To: <87r4x27gh0.fsf@ti.com>

On Fri, Mar 9, 2012 at 2:42 AM, Kevin Hilman <khilman@ti.com> wrote:
> Hi Tomi,
>
> A while ago you were asking about why DSS pwrdm counts were so high on
> OMAP3, and why DSS was transitioning even though it was completely
> unused. Paul and I just spent some a little time debugging this, and
> narrowed it down to autodeps. (sorry it took so long, it finally
> bothered me enough to actually look into it.)

I've seen the same happening to usbhost_pwrdm in linux-next, maybe it
needs similar patch?

Talking about linux-next, musb is crashing there on first register
access, just after pm_runtime_get_sync(), maybe something's up with
clock related code? CONFIG_PM_RUNTIME was enabled there.


-- 
Gražvydas
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-03-09 11:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09  0:42 DSS pwrdm usecount, disabling autodeps for DSS Kevin Hilman
2012-03-09 11:08 ` Grazvydas Ignotas [this message]
2012-03-09 11:14 ` Tomi Valkeinen
2012-03-09 17:57   ` Paul Walmsley
2012-03-12  9:00     ` Tomi Valkeinen
2012-03-12 16:24       ` Kevin Hilman
2012-03-09 18:17   ` 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='CANOLnOOdnJ4OGrhBdF5h_NyYHZ4FPsJet+0M=fGCygQDOsWByQ@mail.gmail.com' \
    --to=notasas@gmail.com \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=tomi.valkeinen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).