public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: "DebBarma, Tarun Kanti" <tarun.kanti@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v8 0/11] dmtimer adaptation to platform_driver
Date: Thu, 06 Jan 2011 08:21:17 -0800	[thread overview]
Message-ID: <87pqsaypdu.fsf@ti.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB0373D2F5FA@dbde02.ent.ti.com> (Tarun Kanti DebBarma's message of "Thu, 6 Jan 2011 19:04:55 +0530")

Hi Tarun,

"DebBarma, Tarun Kanti" <tarun.kanti@ti.com> writes:

>> >
>> > Also, testing with PM on 34xx/n900, I noticed that this series prevents
>> > PER and CORE from hitting retention during suspend.  I haven't debugged
>> > why yet.
>> I have not done power testing. I will try this out right away and confirm.
>>
> Here is a brief update on pm test.
>
> (1) Without dmtimer patch series:
> [  305.641204] Powerdomain (core_pwrdm) didn't enter target state 1
> [  305.647491] Could not enter target state in pm_suspend

What board is this on?

Indeed some platforms do not hit CORE retention by default, most often
because of the boot loader leaving some devices in a state that prevents
them from idling.

At least on 34xx/n900 (with DSS enabled), core is hitting retention for
me.  On Beagle, I have to also use my pm-otg-reset branch to ensure that
the MUSB block is properly reset on boot, othewise MUSB is preventing
CORE RET.  I suspect this would be the same problem on 3430SDP.

> (2) With dmtimer patch series:
> [   25.291503] Powerdomain (core_pwrdm) didn't enter target state 1
> [   25.297790] Powerdomain (per_pwrdm) didn't enter target state 1
> [   25.303985] Could not enter target state in pm_suspend
>
> I will debug further.

Thanks, you can see from this that something in the dmtimer series is
preventing PER from hitting retention.

Kevin

  reply	other threads:[~2011-01-06 16:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05 11:48 [PATCH v8 0/11] dmtimer adaptation to platform_driver Tarun Kanti DebBarma
2011-01-05 11:48 ` [PATCH v8 1/11] OMAP2+: dmtimer: add device names to flck nodes Tarun Kanti DebBarma
2011-01-05 11:48 ` [PATCH v8 2/11] OMAP2420: hwmod data: add dmtimer Tarun Kanti DebBarma
2011-01-05 11:48 ` [PATCH v8 3/11] OMAP2430: " Tarun Kanti DebBarma
2011-01-05 11:48 ` [PATCH v8 4/11] OMAP3: " Tarun Kanti DebBarma
2011-01-06  0:44   ` Kevin Hilman
2011-01-06  6:12     ` DebBarma, Tarun Kanti
2011-01-05 11:48 ` [PATCH v8 5/11] OMAP4: " Tarun Kanti DebBarma
2011-01-05 11:48 ` [PATCH v8 6/11] OMAP1: dmtimer: conversion to platform devices Tarun Kanti DebBarma
2011-01-05 23:51   ` Kevin Hilman
2011-01-06  9:28     ` DebBarma, Tarun Kanti
2011-01-05 11:48 ` [PATCH v8 7/11] OMAP2+: dmtimer: convert " Tarun Kanti DebBarma
2011-01-05 11:48 ` [PATCH v8 8/11] OMAP: dmtimer: platform driver Tarun Kanti DebBarma
2011-01-05 11:48 ` [PATCH v8 9/11] OMAP: dmtimer: switch-over to platform device driver Tarun Kanti DebBarma
2011-01-05 11:48 ` [PATCH v8 10/11] OMAP: dmtimer: pm_runtime support Tarun Kanti DebBarma
2011-01-05 11:48 ` [PATCH v8 11/11] OMAP: dmtimer: add timeout to low-level routines Tarun Kanti DebBarma
2011-01-06  1:03 ` [PATCH v8 0/11] dmtimer adaptation to platform_driver Kevin Hilman
2011-01-06  5:57   ` DebBarma, Tarun Kanti
2011-01-06 13:34     ` DebBarma, Tarun Kanti
2011-01-06 16:21       ` Kevin Hilman [this message]
2011-01-10 11:15         ` DebBarma, Tarun Kanti
2011-01-06 16:17     ` Kevin Hilman
2011-01-10 11:10       ` DebBarma, Tarun Kanti

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=87pqsaypdu.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tarun.kanti@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