From: Kevin Hilman <khilman@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
Paul Walmsley <paul@pwsan.com>, Benoit Cousson <b-cousson@ti.com>
Subject: Re: DSS pwrdm usecount, disabling autodeps for DSS
Date: Fri, 09 Mar 2012 10:17:41 -0800 [thread overview]
Message-ID: <87obs53agq.fsf@ti.com> (raw)
In-Reply-To: <1331291641.1927.38.camel@deskari> (Tomi Valkeinen's message of "Fri, 09 Mar 2012 13:14:01 +0200")
Tomi Valkeinen <tomi.valkeinen@ti.com> writes:
> On Thu, 2012-03-08 at 16:42 -0800, Kevin Hilman 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.)
>>
>> The patch below fixes the problem at least when DSS is not loaded (DSS
>> just stays in retention), but I didn't try this with any active DSS
>> usage, or loading/unloding the DSS drivers.
>>
>> Could you give the patch below a try on OMAP3 along with some active DSS
>> usage as well as unloading the modules after using. Could you also
>> verify that suspend/resume continues to work for DSS?
>
> I didn't get very far with the patch =(. Tested on omap3 overo, with
> -rc6 based dss tree.
Bummer, thanks for trying.
It seems we still have work to do in fixing the omap2/3 enable sequence.
At least we know the root cause of the DSS pwrdm usecount now.
Kevin
prev parent reply other threads:[~2012-03-09 18:17 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
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 [this message]
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=87obs53agq.fsf@ti.com \
--to=khilman@ti.com \
--cc=b-cousson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.