linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] ARM: cpuidle: davinci: Fix target residency
Date: Thu, 11 Jul 2013 13:53:26 +0200	[thread overview]
Message-ID: <51DE9CB6.40706@linaro.org> (raw)
In-Reply-To: <51CD3063.5010309@ti.com>

On 06/28/2013 08:42 AM, Sekhar Nori wrote:
> On 6/27/2013 8:40 PM, Daniel Lezcano wrote:
>> The commit 19976c2a88d125aec16b9255c7197c297bbdd637 changed the target
>> residency to 100000, assuming this is a careless mistake.
>>
>> commit 19976c2a88d125aec16b9255c7197c297bbdd637
>> Author: Robert Lee <rob.lee@linaro.org>
>> Date:   Tue Mar 20 15:22:45 2012 -0500
>>
>>     ARM: davinci: Consolidate time keeping and irq enable
>>
>>     Enable core cpuidle timekeeping and irq enabling and remove that
>>     handling from this code.
>>
>>     Signed-off-by: Robert Lee <rob.lee@linaro.org>
>>     Reviewed-by: Kevin Hilman <khilman@ti.com>
>>     Reviewed-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>>     Acked-by: Jean Pihet <j-pihet@ti.com>
>>     Signed-off-by: Len Brown <len.brown@intel.com>
>>
>> The same happened to the at91's cpuidle driver.
>>
>> Fix it by putting the initial value to 10000.
>>
>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> 
> Acked-by: Sekhar Nori <nsekhar@ti.com>

Hi Sekhar,

I applied this patch on my tree for the next PM pull request.

Thanks
  -- Daniel



-- 
 <http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

      reply	other threads:[~2013-07-11 11:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 15:10 [PATCH V2] ARM: cpuidle: davinci: Fix target residency Daniel Lezcano
2013-06-28  6:42 ` Sekhar Nori
2013-07-11 11:53   ` Daniel Lezcano [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=51DE9CB6.40706@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).